Communications architecture for intelligent electronic devices

ABSTRACT

A power management architecture for an electrical power distribution system, or portion thereof, is disclosed. The architecture includes multiple intelligent electronic devices (“IED&#39;s”) distributed throughout the power distribution system to manage the flow and consumption of power from the system using real time communications. Power management application software and/or hardware components operate on the IED&#39;s and the back-end servers and inter-operate via the network to implement a power management application. The architecture provides a scalable and cost effective framework of hardware and software upon which such power management applications can operate to manage the distribution and consumption of electrical power by one or more utilities/suppliers and/or customers which provide and utilize the power distribution system. Autonomous communication on the network between TED&#39;s, back-end servers an other entities is facilitated by the use of an instant message protocol and server and associated applications, which offer reliable and determinate message delivery.

RELATED APPLICATIONS

[0001] This application is a continuation-in-part under 37 C.F.R. §1.53(b) of U.S. patent application Ser. No. 09/723,564 filed Nov. 28,2000 (Attorney Docket No. 6270/48) now U.S. Pat. No. ______, the entiredisclosure of which is hereby incorporated by reference and U.S. patentapplication Ser. No. 09/814,436 filed Mar. 22, 2001 (Attorney Docket No.6270/60) now U.S. Pat. No. ______, the entire disclosure of which ishereby incorporated by reference.

BACKGROUND

[0002] With the advent of high technology needs and market deregulation,today's energy market has become very dynamic. High technologyindustries have increased their demands on the electrical powersupplier, requiring more power, increased reliability and lower costs. Atypical computer data center may use 100 to 300 watts of energy persquare foot compared to an average of 15 watts per square foot for atypical commercial building. Further, an electrical outage, whether itis a complete loss of power or simply a drop in the delivered voltage,can cost these companies millions of dollars in down time and lostbusiness.

[0003] In addition, deregulation of the energy industry is allowing bothindustrial and individual consumers the unprecedented capability tochoose their supplier which is fostering a competitive supply/demanddriven market in what was once a traditionally monopolistic industry.

[0004] Network communications, such as electronic mail transportprotocols, are increasingly utilized in this dynamic market. Althoughemail offers a robust delivery of communications there is often noguarantee of the message being communicated and real time communicationsis not always available.

[0005] These requirements of increased demand and higher reliability areburdening an already overtaxed distribution network and forcingutilities to invest in infrastructure improvements at a time when thederegulated competitive market is forcing them to cut costs and lowerprices. Accordingly, there is a need for a real time system of managingthe distribution and consumption of electrical power which meets theincreased demands of users and allows the utility supplier to compete ina deregulated competitive marketplace.

SUMMARY

[0006] The present invention is defined by the following claims, andnothing in this section should be taken as a limitation on those claims.By way of introduction, the preferred embodiments described below relateto an electrical power management architecture. The architecturecomprises a network, at least one electric meter coupled with thenetwork, and an instant message server coupled with the electric meterand the network, the electric meter operative to generate a firstinstant message to the instant message server and receive a secondinstant message from the server.

[0007] The preferred embodiments further relate to a method ofmonitoring presence of at least one intelligent electronic device(“IED”) in an electrical power management architecture. In oneembodiment, the method comprises coupling the IED with a network, theIED being characterized by the presence; transmitting, autonomously, thepresence of the IED onto the network; receiving the presence of the IEDat a presence server coupled with the network; and monitoring thepresence of the IED.

[0008] Further aspects and advantages of the invention are discussedbelow in conjunction with the preferred embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009]FIG. 1 illustrates a first embodiment of the Power ManagementArchitecture.

[0010]FIG. 2a illustrates an IED, for use with the embodiment of FIG. 1,containing several power management components.

[0011]FIG. 2b illustrates another IED, for use with the embodiment ofFIG. 1, containing several power management components.

[0012]FIG. 3a illustrates an IED, for use with the embodiment of FIG. 1,connected to a power system.

[0013]FIG. 3b illustrates the internal components of an IED for use withthe embodiment of FIG. 1.

[0014]FIG. 3c illustrates a preferred protocol stack of an IED for usewith the embodiment of FIG. 1.

[0015]FIG. 4a illustrates an IED, for use with the embodiment of FIG. 1,coupled with power management components.

[0016]FIG. 4b illustrates the use of a power management applicationcomponent.

[0017]FIG. 5a illustrates a preferred embodiment with multiple energysuppliers.

[0018]FIG. 5b illustrates a preferred method of managing multiplesuppliers for use with the embodiment of FIG. 1.

[0019]FIG. 6 illustrates a second embodiment using a distributed powermanagement component.

[0020]FIG. 7 illustrates a third embodiment using a power reliabilitycomponent.

[0021]FIG. 8 illustrates a fourth embodiment using a peer to peercomponent.

[0022]FIG. 9 illustrates an IED, for use with the embodiment of FIG. 1,transmitting data to multiple recipients.

[0023]FIG. 10 illustrates a monitoring server, for use with theembodiment of FIG. 1, receiving data from an IED.

[0024]FIG. 11 illustrates an exemplary display generated by theembodiment of FIG. 10.

[0025]FIG. 12 illustrates a first embodiment of a networked architecturewith firewalls.

[0026]FIG. 13 illustrates a second embodiment of a networkedarchitecture with firewalls.

[0027]FIG. 14 illustrates a third embodiment of a networked architecturewith firewalls.

[0028]FIG. 15a illustrates a network with an instant message serverresiding on the network.

[0029]FIG. 15b illustrates an architecture that allows a client to showits status or presence to an instant message server.

[0030]FIG. 15c illustrates the architecture involved for the server toreceive and update the presence of clients in a centralized instantmessage application.

[0031]FIG. 16 illustrates an example communications architectureincluding devices utilizing an instant message server.

[0032]FIG. 17 illustrates an instant message server connected to abranch circuit system.

DETAILED DESCRIPTION OF THE PRESENTLY PREFERRED EMBODIMENTS

[0033] Intelligent electronic devices (“IED's”) such as programmablelogic controllers (“PLC's”), Remote Terminal Units (“RTU's”),electric/watt hour meters, protection relays and fault recorders arewidely available that make use of memory and microprocessors to provideincreased versatility and additional functionality. Such functionalityincludes the ability to communicate with remote computing systems,either via a direct connection, e.g. modem or via a network. For moredetailed information regarding IED's capable of network communication,please refer to U.S. patent application Ser. No. 09/723,564, entitled“INTRA-DEVICE COMMUNICATIONS ARCHITECTURE FOR MANAGING ELECTRICAL POWERDISTRIBUTION AND CONSUMPTION” and U.S. patent application Ser. No.09/814,436, entitled “COMMUNICATIONS ARCHITECTURE FOR INTELLIGENTELECTRONIC DEVICES”, captioned above. In particular, the monitoring ofelectrical power, especially the measuring and calculating of electricalparameters, provides valuable information for power utilities and theircustomers. Monitoring of electrical power is important to ensure thatthe electrical power is effectively and efficiently generated,distributed and utilized. More importantly, monitoring of the electricalpower in real time, and responding to the monitored results in realtime, can give tremendous cost savings in today's marketplace.Monitoring is often done by use of email, where the email offers a threephases in a message transfer: 1) email is there or, 2) email is notthere or, 3) email is on it's way. The third state gives uncertainty asan email message may be delayed while routing through the network or,worse yet, diverted and lost. With the dynamic market place today, wherepower consumption and their associated fortunes can be made or lost inseconds, a user must be able to respond immediately in real time and cannot afford to have the indeterminate “email communication is on it'sway”.

[0034] Various different arrangements are presently available formonitoring, measuring, and controlling power parameters. Typically, anIED, such as an individual power measuring device, is placed on a givenbranch or line proximate to one or more loads which are coupled with thebranch or line in order to measure/monitor power system parameters.Herein, the phrase “coupled with” is defined to mean directly connectedto or indirectly connected with through one or more intermediatecomponents. Such intermediate components may include both hardware andsoftware based components. In addition to monitoring power parameters ofa certain load(s), such power monitoring devices have a variety of otherapplications. For example, power monitoring devices can be used insupervisory control and data acquisition (“SCADA”) systems such as theXA/21 Energy Management System manufactured by GE Harris Energy ControlSystems located in Melbourne, Fla.

[0035] In a typical SCADA application, IED's/power measuring devicesindividually dial-in to a central SCADA computer system via a modem.However, such dial-in systems are limited by the number of inboundtelephone lines to the SCADA computer and the availability of phoneservice access to the IED/power measuring devices. With a limited numberof inbound telephone lines, the number of IED's/power measuring devicesthat can simultaneously report their data is limited resulting inlimited data throughput and delayed reporting. Further, while cellularbased modems and cellular system access are widely available, providinga large number of power measuring devices with phone service iscumbersome and often cost prohibitive. The overall result is a systemthat is not easily scalable to handle a large number of IED's/powermeasuring devices or the increased bandwidth and throughput requirementsof advanced power management applications. However, the ability to use acomputer network infrastructure, such as the Internet, allows for theuse of power parameter and data transmission and reporting on a largescale. The Internet provides a connectionless point to pointcommunications medium that is capable of supporting substantiallysimultaneous communications among a large number of devices. For examplethis existing Internet infrastructure can be used to simultaneously pushout billing, load profile, or power quality data to a large number ofIED/power measurement and control devices located throughout a powerdistribution system that can be used by those devices to analyze or makeintelligent decisions based on power consumption at their locations. Thebandwidth and throughput capabilities of the Internet supports theadditional requirements of advanced power management applications. Forexample, billing data, or other certified revenue data, must betransferred through a secure process which prevents unauthorized accessto the data and ensures receipt of the data by the appropriate device orentity. Utilizing the Internet, communications can be encrypted such asby using encrypted email. Further, encryption authentication parameterssuch as time/date stamp or the IED serial number, can be employed.Within the Internet, there are many other types of communicationsapplications that may be employed to facilitate the above describedinter-device communications such as email, Telnet, file transferprotocol (“FTP”), trivial file transfer protocol (“TFTP”) or proprietarysystems, both unsecured and secure/encrypted.

[0036] As used herein, Intelligent electronic devices (“IED's”) includeProgrammable Logic Controllers (“PLC's”), Remote Terminal Units(“RTU's”), electric power meters, protective relays, fault recorders andother devices which are coupled with power distribution networks tomanage and control the distribution and consumption of electrical power.Such devices typically utilize memory and microprocessors executingsoftware to implement the desired power management function. IED'sinclude on-site devices coupled with particular loads or portions of anelectrical distribution system and are used to monitor and manage powergeneration, distribution and consumption. IED's are also referred hereinas power management devices (“PMD's”).

[0037] A Remote Terminal Unit (“RTU”) is a field device installed on anelectrical power distribution system at the desired point of metering.It is equipped with input channels (for sensing or metering), outputchannels (for control, indication or alarms) and a communications port.Metered information is typically available through a communicationprotocol via a serial communication port. An exemplary RTU is the XPSeries, manufactured by Quindar Productions Ltd. in Mississauga,Ontario, Canada.

[0038] A Programmable Logic Controller (“PLC”) is a solid-state controlsystem that has a user-programmable memory for storage of instructionsto implement specific functions such as Input/output (I/O) control,logic, timing, counting, report generation, communication, arithmetic,and data file manipulation. A PLC consists of a central processor,inputoutput interface, and memory. A PLC is designed as an industrialcontrol system. An exemplary PLC is the SLC 500 Series, manufactured byAllen-Bradley in Milwaukee, Wis.

[0039] A meter, is a device that records and measures power events,power quality, current, voltage waveforms, harmonics, transients andother power disturbances. Revenue accurate meters (“revenue meter”)relate to revenue accuracy electrical power metering devices with theability to detect, monitor, report, quantify and communicate powerquality information about the power which they are metering. Anexemplary meter is the model 8500 meter, manufactured by PowerMeasurement Ltd, in Saanichton, B.C. Canada.

[0040] A protective relay is an electrical device that is designed tointerpret input conditions in a prescribed manner, and after specifiedconditions are met, to cause contact operation or similar abrupt changein associated electric circuits. A relay may consist of several relayunits, each responsive to a specified input, with the combination ofunits providing the desired overall performance characteristics of therelay. Inputs are usually electric but may be mechanical, thermal orother quantity, or a combination thereof. An exemplary relay is the typeN and KC, manufactured by ABB in Raleigh, N.C.

[0041] A fault recorder is a device that records the waveform anddigital inputs, such as breaker status which resulting from a fault in aline, such as a fault caused by a break in the line. An exemplary faultrecorder is the IDM, manufactured by Hathaway Corp in Littleton, Colo.

[0042] IED's can also be created from existing electromechanical metersor solid-state devices by the addition of a monitoring and controldevice which converts the mechanical rotation of the rotary counter intoelectrical pulses or monitors the pulse output of the meter. Anexemplary electromechanical meter is the AB1 Meter manufactured by ABBin Raleigh, N.C. Such conversion devices are known in the art.

[0043] This invention describes a communications architecture that canbe used for monitoring, protection and control of devices and electricalpower distribution in an electrical power distribution system, whereIED's can interact with other IED's and attached devices.

[0044] As will be described in more detail below, a power managementarchitecture for an electrical power distribution system, or portionthereof, is disclosed. The architecture provides a scalable and costeffective framework of hardware and software upon which power managementapplications can operate to manage the distribution and consumption ofelectrical power by one or more utilities/suppliers and/or customerswhich provide and utilize the power distribution system.

[0045] Power management applications include automated meter readingapplications, load shedding applications, deregulated suppliermanagement applications, on-site power generation managementapplications, power quality management applications, protection/safetyapplications, and general distribution system management applications,such as equipment inventory and maintenance applications. A powermanagement application typically includes one or more applicationcomponents which utilize the power management architecture tointeroperate and communicate thereby implementing the power managementapplication.

[0046] The architecture includes Intelligent Electronic Devices(“IED's”) distributed throughout the power distribution system tomonitor and control the flow of electrical power. IED's may bepositioned along the supplier's distribution path or within a customer'sinternal distribution system. IED's include revenue electric watt-hourmeters, protection relays, programmable logic controllers, remoteterminal units, fault recorders and other devices used to monitor and/orcontrol electrical power distribution and consumption. As was noted,IED's also include legacy mechanical or electromechanical devices whichhave been retrofitted with appropriate hardware and/or software so as tobe able to integrate with the power management architecture. Typicallyan IED is associated with a particular load or set of loads which aredrawing electrical power from the power distribution system. As wasdescribed above, the IED may also be capable of receiving data from orcontrolling its associated load. Depending on the type of IED and thetype of load it may be associated with, the IED implements a powermanagement function such as measuring power consumption, controllingpower distribution such as a relay function, monitoring power quality,measuring power parameters such as phasor components, voltage orcurrent, controlling power generation facilities, or combinationsthereof. For functions which produce data or other results, the IED canpush the data onto the network to another IED or back end server,automatically or event driven, (discussed in more detail below) or theIED can wait for a polling communication which requests that the data betransmitted to the requester.

[0047] In addition, the IED is also capable of implementing anapplication component of a power management application utilizing thearchitecture. As was described above and further described below, thepower management application includes power management applicationcomponents which are implemented on different portions of the powermanagement architecture and communicate with one another via thearchitecture network. The operation of the power management applicationcomponents and their interactions/communications implement the powermanagement application. One or more power management applications may beutilizing the architecture at any given time and therefore, the IED mayimplement one or more power management application components at anygiven time.

[0048] The architecture further includes a communications network.Preferably, the communication network is a publicly accessible datanetwork such as the Internet or other network or combination ofsub-networks that transmit data utilizing the transmission controlprotocol/internet protocol (“TCP/IP”) protocol suite. Such networksinclude private intranet networks, virtual private networks, extranetsor combinations thereof and combinations which include the Internet.Alternatively, other communications network architectures may also beused. Each IED preferably includes the software and/or hardwarenecessary to facilitate communications over the communications networkby the hardware and/or software which implements the power managementfunctions and power management application components. In alternativeembodiments, quality of service protocols can be implemented toguarantee timely data delivery, especially in real time applications.

[0049] The hardware and/or software which facilitate networkcommunications preferably includes a communications protocol stack whichprovides a standard interface to which the power management functionshardware/software and power management application componentshardware/software interact. As will be discussed in more detail below,in one embodiment, the communications protocol stack is a layeredarchitecture of software components. In the preferred embodiments theselayers or software components include an applications layer, a transportlayer, a routing layer, a switching layer and an interface layer.

[0050] The applications layer includes the software which implements thepower management functions and the power management applicationscomponents. Further, the applications layer also includes thecommunication software applications which support the available methodsof network communications. Typically, the power management functionsoftware interacts with the power management hardware to monitor and orcontrol the portion of the power distribution system and/or the loadcoupled with the IED. The application component typically interacts withthe power management function software to control the power managementfunction or process data monitored by the power management function. Oneor both of the power management function software and the powermanagement application component software interacts with thecommunication software applications in order to communicate over thenetwork with other devices.

[0051] The communications applications include electronic mail clientapplications such as applications which support SMTP, MIME or POPnetwork communications protocols, security client applications such asencryption/decryption or authentication applications such as secure-HTTPor secure sockets layer (“SSL”), or other clients which support standardnetwork communications protocols such as telnet, hypertext transportprotocol (“HTTP”), file transfer protocol (“FTP”), network news transferprotocol (“NNTP”), instant messaging client applications, orcombinations thereof. Other client application protocols includeextensible markup language (“XML”) client protocol and associatedprotocols such as Simple Object Access Protocol (“SOAP”). Further, thecommunications applications could also include client applications whichsupport peer to peer communications. All of the communicationsapplications preferably include the ability to communicate via thesecurity client applications to secure the communications transmittedvia the network from unauthorized access and to ensure that receivedcommunications are authentic, uncompromised and received by the intendedrecipient. Further, the communications applications include the abilityto for redundant operation through the use of one or more interfacelayer components (discussed in more detail below), error detection andcorrection and the ability to communicate through firewalls or similarprivate network protection devices.

[0052] The transport layer interfaces the applications layer to therouting layer and accepts communications from the applications layerthat are to be transmitted over the network. The transport layer breaksup the communications layer into one or more packets, augments eachpacket with sequencing data and addressing data and hands each packet tothe routing layer. Similarly, packets which are received from thenetwork are reassembled by the transport layer and the re-constructedcommunications are then handed up to the applications layer and theappropriate communications applications client. The transport layer alsoensures that all packets which make up a given transmission are sent orreceived by the intended destination. Missing or damaged packets arere-requested by the transport layer from the source of thecommunication. In the preferred embodiment, the transport layerimplements the Transmission control protocol (“TCP”).

[0053] The routing layer interfaces the transport layer to the switchinglayer. The routing layer routes each packet received from the transportlayer over the network. The routing layer augments each packet with thesource and destination address information. In the preferred embodiment,the routing layer implements the internet protocol (“IP”). It will beappreciated that the TCP/IP protocols implement a connectionless packetswitching network which facilitates scalable substantially simultaneouscommunications among multiple devices.

[0054] The switching layer interfaces the routing layer to the interfacelayer. The switching layer and interface layer are typically integrated.The interface layer comprises the actual hardware interface to thenetwork. The interface layer may include an Ethernet interface, a modem,such as wired modem using the serial line interface protocol (“SLIP”) orpoint to point protocol (“PPP”), wired modem which may be an analog ordigital modem such as a integrated services digital network (“ISDN”)modem or digital subscriber line (“DSL”) modem, or a cellular modem.Further, other wireless interfaces, such as Bluetooth, may also be used.In addition, AC power line data network interface may also be used.Cellular modems further provide the functionality to determine thegeographic location of the IED using cellular RF triangulation. Suchlocation information can be transmitted along with other powermanagement data as one factor used in authenticating the transmitteddata. In the preferred embodiments, the interface layer provided allowsfor redundant communication capabilities. The interface layer couplesthe IED with a local area network, such as provided at the customer orutility site. Alternatively, the interface layer can couple the IED witha point of presence provided by a local network provider such as aninternet service provider (“ISP”).

[0055] Finally, the architecture includes back-end server computers ordata collection devices. Back end servers may be provided by theconsumer of electric power, the utility supplier of electric power or athird party. In one embodiment, these devices are IED's themselves. Theback end servers are also coupled with the network in a same way as theIED's and may also include a communication protocol stack. The back endservers also implement power management applications components whichinteract and communicate with the power management applicationcomponents on the IED's to accomplish the power management application.Preferably, the IED's are programmed with the network addresses of theappropriate back end servers or are capable of probing the network forback end servers to communicate with. Similarly, the back end server isprogrammed with the network addresses of one or more affiliate IED's oris capable of probing the network to find IED's that are connected. Ineither case of network probing by the IED or back-end server, softwareand/or hardware is provided to ensure that back-end servers communicatewith authorized IED's and vice versa allowing multiple customers andmultiple suppliers to utilize the architecture for various powermanagement applications without interfering with each other.

[0056] The back end servers preferably are executing softwareapplication counterparts to the application clients and protocolsoperating on the IED's such as electronic mail, HTTP, FTP, telnet, NNTPor XML servers which are designed to receive and process communicationsfrom the IED's. Exemplary server communications applications includeMicrosoft Exchange™. The back end server is therefore capable ofcommunicating, substantially simultaneously, with multiple IED's at anygiven time. Further, the back end server implements a securityapplication which decrypts and/or authenticates communications receivedfrom IED's and encrypts communications sent to IED's.

[0057] In one embodiment, software executing on the back end serverreceives communications from an IED and automatically extracts the datafrom the communication. The data is automatically fed to a powermanagement application component, such as a billing managementcomponent.

[0058] In this way, a generally accessible connectionless/scalablecommunications architecture is provided for operating power managementapplications. The architecture facilitates IED-supplier communicationsapplications such as for automated meter reading, revenue collection,IED tampering and fraud detection, power quality monitoring, load orgeneration control, tariff updating or power reliability monitoring. Thearchitecture also supports IED-consumer applications such as usage/costmonitoring, IED tampering and fraud detection, power quality monitoring,power reliability monitoring or control applications such as loadshedding/cost control or generation control. In addition, real timederegulated utility/supplier switching applications which respond inreal time to energy costs fluctuations can be implemented whichautomatically switch suppliers based on real time cost. Further thearchitecture supports communications between IED's such as early warningsystems which warn downstream IED's of impending power quality events.The architecture also supports utility/supplier to customer applicationssuch as real time pricing reporting, billing reporting, power quality orpower reliability reporting. Customer to customer applications may alsobe supported wherein customers can share power quality or powerreliability data.

[0059] As used herein, an IED or PMD is a power management devicecapable of network communication. A back end server is a data collectionor central command device coupled with the network which receives powermanagement data from an IED and/or generates power management commandsto and IED. An IED may contain a back-end server. The network is anycommunications network which supports the Transmission ControlProtocol/Internet Protocol (“TCP/IP”) network protocol suite. In thepreferred embodiment IED's include devices such as PLC's, RTU's, meters,protection relays, fault recorders or modified electromechanical devicesand further include any device which is coupled with an electrical powerdistribution network, or portion thereof, for the purpose of managing orcontrolling the distribution or consumption of electrical power.

[0060]FIG. 1 illustrates an overview of the preferred embodiment of thePower Management Architecture (“architecture”) 100, which contains oneor more IED's 102, 103, 104, 105, 106, 107, 108, 109. The IED's 102-109are connected to an electrical power distribution system 101, or portionthereof, to measure, monitor and control quality, distribution andconsumption of electric power from the system 101, or portion thereof.The power distribution system is typically owned by either autility/supplier or consumer of electric power however some componentsmay be owned and/or leased from third parties. The IED's 102-109 arefurther interconnected with each other and back end servers 121, 122,123, 124 via a network 110 to implement a Power Management Application(“application”) 111 (not shown). In the preferred embodiment, thenetwork 110 is the Internet. Alternatively, the network 110 can be aprivate or public intranet, an extranet or combinations thereof, or anynetwork utilizing the Transmission Control Protocol/Internet Protocol(“TCP/IP”) network protocol suite to enable communications, including IPtunneling protocols such as those which allow virtual private networkscoupling multiple intranets or extranets together via the Internet. Thenetwork 110 may also include portions or sub-networks which use wirelesstechnology to enable communications, such as RF, cellular or Bluetoothtechnologies. The network 110 preferably supports application protocolssuch as telnet, FTP, POP3, SMTP, NNTP, Mime, HTTP, SMTP, SNNP, IMAP,proprietary protocols or other network application protocols as areknown in the art as well as transport protocols SLIP, PPP, TCP/IP andother transport protocols known in the art.

[0061] The Power Management Application 111 utilizes the architecture100 and comprises power management application components whichimplement the particular power management functions required by theapplication 111. The power management application components are locatedon the IED 102-109 or on the back end server 121-124, or combinationsthereof, and can be a client component, a server component or a peercomponent. Application components communicate with one another over thearchitecture 100 to implement the power management application 111.

[0062] In one preferred embodiment the architecture 100 comprises IED's102-109 connected via a network 110 and back end servers 120, 121, 122,123, 124 which further comprise software which utilizes protocol stacksto communicate. IED's 102-109 can be owned and operated byutilities/suppliers 130, 131, consumers 132 133 or third parties 134 orcombinations thereof. Back end servers 120 121122 123 124 can be ownedby utilities/suppliers 130, 131, consumers 132, 133, third parties 134or combinations thereof. For example, an IED 102-109 is operable tocommunicate directly over the network with the consumer back-end server120, 121, another IED 102-19 or a utility back end server 123,124. Inanother example, a utility back end server 123, 124 is operable toconnect and communicate directly with customer back end servers 120,121. Further explanation and examples on the types of data andcommunication between IED's 102-109 are given in more detail below.

[0063] Furthermore, the architecture's 100 devices, such as the back endservers 120-124 or IED's 102-109, can contain an email server andassociated communications hardware and software such as encryption anddecryption software. Other transfer protocols, such as file transferprotocols (FTP), Simple Object Access Protocol (SOAP), HTTP, XML orother protocols know in the art may also be used in place of electronicmail. Hypertext Transfer Protocol (HTTP) is an application protocol thatallows transfer of files to devices connected to the network. FTP is astandard internet protocol that allows exchange of files between devicesconnected on a network. Extensible markup language (XML) is a fileformat similar to HTML that allows transfer of data on networks. XML isa flexible, self describing, vendor-neutral way to create commoninformation formats and share both the format and the data over theconnection. In the preferred embodiment the data collection server isoperable by either the supplier/utility 123, 124 or the customer 132,133 of the electrical power distribution system 101. SOAP allows aprogram running one kind of operating system to communicate with thesame kind, or another kind of operating system, by using HTTP and XML asmechanisms for the information exchange.

[0064] Furthermore, the application 111 includes an authentication andencryption component which encrypts commands transmitted across thenetwork 110, and decrypts power management data received over thenetwork 110. Authentication is also performed for commands or data sentor received over the network 110. Authentication is the process ofdetermining and verifying whether the IED 102-109 transmitting data orreceiving commands is the IED 102-109 it declares itself to be and inthe preferred embodiment authentication includes parameters such astime/date stamps, digital certificates, physical locating algorithmssuch as cellular triangulation, serial or tracking ID's, which couldinclude geographic location such as longitude and latitude.Authentication prevents fraudulent substitution of IED 102-109 devicesor spoofing of IED 102-109 data generation in an attempt to defraud.Authentication also minimizes data collection and power distributionsystem 101 control errors by verifying that data is being generated andcommands are being received by the appropriate devices. In the preferredembodiment encryption is done utilizing Pretty Good Privacy (PGP). PGPuses a variation of public key system, where each user has a publiclyknown encryption key and a private key known only to that user. Thepublic key system and infrastructure enables users of unsecurednetworks, such as the internet, to securely and privately exchange datathrough the use of public and private cryptographic key pairs.

[0065] In the preferred embodiment the architecture is connectionlesswhich allows for substantially simultaneous communications between asubstantial number of IED's within the architecture. This form ofscalability eclipses the current architectures that utilize point topoint connections, such as provided by telephony networks, betweendevices to enable communications which limit the number of simultaneouscommunications that may take place.

[0066]FIG. 2a illustrates a preferred embodiment where and IED 200contains several power management components 201 202 203 and powermanagement circuitry 220. The power management circuitry 220 is operableto implement the IED's functionality, such as metering/measuring powerdelivered to the load 218 from the electrical power distribution system216, measuring and monitoring power quality, implementing a protectionrelay function, or other functionality of the IED 200. The IED 200further includes a power management application components 211 coupledwith the circuitry 220 and a protocol stack 212 and data communicationinterface 213. The protocol stack 212 and data communications interface213 allow the IED 200 to communicate over the network 215. It will beappreciated that, as described below, the protocol stack 212 may includean interface layer which comprises the data communications interface213. The power management application components 211 include softwareand/or hardware components which, alone, or in combination with othercomponents, implement the power management application 111. Thecomponents 211 may include components which analyze and log themetered/measured data, power quality data or control operation of theIED 200, such as controlling a relay circuit. The components 211 furtherinclude software and/or hardware which processes and communicates datafrom the IED 200 to other remote devices over the network 215, such asback end servers 121-124 or other IED's 200 (102-109), as will bedescribed below. For example, the IED 200 is connected to a load 218.The power management circuitry 220 includes data logging softwareapplications, memory and a CPU, which are configured to store kWh datafrom the load 218 in a memory contained within the power managementcircuitry. The stored data is then read and processed by the components201 202 in the power management application 211. The componentscommunicate with operating system components which contain the protocolstack 212 and the processed data is passed over the network 215 to theappropriate party via the data communications interface 213. One or moreof the components 211 may communicate with one or more applicationcomponents located on one or other IED's 200 and/or one or more back endservers 121-124.

[0067]FIG. 2b illustrates an alternate preferred embodiment where an IED240 is provided which includes power management application components290. A load 280 is connected to an IED 240 via the electrical powerdistribution system 281. The IED 240 is further connected to the network283. The IED 240 contains power management circuitry which is operableto implement the IED's functionality, such as receiving power andgenerating data from the load 280. The IED further includes a protocolstack layer 284 and a data communication interface 286 which allows theback end server to communicate over the network 283. The powermanagement application components 290 include one or more componentssuch as data collection component 250, an automated meter readingcomponent 253 and a billing/revenue management component 252, which maybe revenue certified, a peer-to-peer power management component 257, ausage and consumption management component 258, a distributed powermanagement component 254, a centralized power management component 255,a load management component 259, an electrical power generationmanagement component 260, an IED inventory component 261, an IEDmaintenance component 262, an IED fraud detection component 263, a powerquality monitoring component 264, a power outage component 265, a devicemanagement component 251, a power reliability component 256, orcombinations thereof. Furthermore, components contained on one IED 240may operate simultaneously with components on an IED 102-109, 200 oranother IED 240 or back end server (not shown). More component detailsand examples are given below.

[0068] In one embodiment the application components comprise softwarecomponents, such as an email server or an XML or HTTP server. Theseservers may include a Microsoft Exchange server or a BizTalkframework/XML compatible server. A Microsoft Exchange™ server is anemail server computer program manufactured by Microsoft Corporation,located in Redmond, Wash., typically operating on a server computerwhich facilitates the reception and transmission of emails, and forwardsemails to the email client programs, such as Microsoft Outlook™, ofusers that have accounts on the server. BizTalk is a computer industryinitiative which promotes XML as the common data exchange for e-commerceand application integration over the internet. BizTalk providesframeworks and guidelines for how to publish standard data structures inXML and how to use XML messages to integrate software components orprograms. Alternately, hardware components, such as a dedicated cellularphone, GPS encryption or decryption key or dongle are included in thecomponents. In a further embodiment, a combination of both hardware andsoftware components are utilized. Additionally, referring back to FIG.1, one or more power management application components 290 can utilizethe architecture 100 to implement their functionality. For example, autility 130 has a back end server 124 which contains power managementapplication and associated components, such as a usage and consumptionmonitoring component 258. The utility 130 supplies power to a consumer132 via the power distribution network 110 and monitors the consumerspower consumption using the power management application components onthe back end server 124 which communicates with the IED's 104, 105, 108via the network 110 to retrieve measured consumption/usage data. Theconsumer 132 concurrently monitors usage of loads 150, using an IED 104,105, 108 which is connected to the network 110, computing real timecosts posted by the utility 130. In one embodiment, the consumer 132monitors usage using back end server 120 which receives usage andconsumption data from the IED's 104, 105, 108 via the network 110. TheIED 104, 105, 108 implements power management application componentssuch as load management components and billing management components.The back end server 120, 124 implements power management applicationcomponents such as a data collection component, a billing/revenuemanagement component, an automated meter reading component or ausage/consumption management component. The components on the IED 104,105, 108 work in concert with the components on the back end server 120,124 via the network 110 to implement the overall power managementapplication. In a further embodiment, one or more power managementapplication components are operating on IED 104, 105, 108 and/or backend servers 120, 124 at any given time. Each power managementapplication can be utilized by one or more users, or differentapplications can be used by different users. Moreover, the applicationcomponents can exist on the same or different IED's 104, 105, 108 orback end servers 120, 124.

[0069] In the preferred embodiment, the data collection component 250enables an IED to collect and collate data from either a single ormultiple sources via the network 110. The data collected by thecomponent is stored and can be retrieved by other components of thepower management application components 290, or other componentsimplemented on other IED's 102-109 located on the network 110. In thepreferred embodiment the Automated Meter Reading component 253 isutilized to allow either the consumers 132, 133 or providers 130, 131 togenerate power management reports from the IED data. In the preferredembodiment the electrical power generation management component 260analyzes data received from IED's 102-109 to either minimize or maximizemeasured or computed values such as revenue, cost, consumption or usageby use of handling and manipulating power systems and load routing. IEDinventory, maintenance and fraud detection component 261, 262, 263receive or request communications from the IED's 102-109 allowing thepower management application to inventory the installed base of IED's102-109, including establishing or confirming their geographicinstallation location, or check the maintenance history of all connectedIED's 102-109 These power management applications aid in confirmingoutage locations or authenticating communications to or from an IED102-109 to prevent fraud and minimize errors. In one embodiment, the IEDinventory component 261 utilizes cellular triangulation technologies, orcaller ID based geographic locator technologies to determine and verifyIED inventories. In the preferred embodiment the fraud detectioncomponent 263 further detects device tampering. In the preferredembodiment the power quality monitoring component 264 monitors andprocesses electric parameters, such as current, voltage and energy whichinclude volts, amps, Watts, phase relationships between waveforms, kWh,kvAr, power factor, and frequency, etc. The power quality monitoringcomponent 264 reports alarms, alerts, warnings and general power qualitystatus, based on the monitored parameters, directly to the appropriateuser, such as customers 132, 133 or utilities 130, 131.

[0070]FIG. 3a illustrates a preferred embodiment of an IED 302 for usewith the disclosed power management architecture 100. The IED 302 ispreferably coupled with a load 301 via a power a distribution system300, or portion thereof. The IED 302 includes device circuitry 305 and adata communications interface 306. The IED 302 is further coupled with anetwork 307. The device circuitry 305 includes the internal hardware andsoftware of the device, such as the CPU 305 a, memory 305 c, firmwareand software applications 305d, data measurement functions 305 b andcommunications protocol stack 305 e. The data communication interface306 couples the device circuitry 305 of the IED 302 with thecommunications network 307. Alternate embodiments may have powermanagement control functions 305 b in place of data measurementcircuitry. For example, a relay may include a control device andcorresponding control functions that regulate electricity flow to a loadbased on preset parameters. Alternately a revenue meter may include datameasurement circuitry that logs and processes data from a connectedload. IED's may contain one or the other or combinations of circuitry.In an alternate embodiment the circuitry includes phasor monitoringcircuits (not shown) which comprise phasor transducers that receiveanalog signals representative of parameters of electricity in a circuitover the power distribution system. Further detail and discussionregarding the phasor circuitry is discussed in U.S. patent applicationSer. No. 08/798,723, captioned above.

[0071]FIG. 3b illustrates a more detailed embodiment of the IED's 310power management application components 311 and protocol stacks. The IED310 includes power management application components 311, acommunications protocol stack 312 and a data communications interface313 (as was noted above, in alternate embodiments, the protocol stack312 may include the data communications interface 313). The applicationcomponents 311 includes a Load management component 315 a, whichmeasures the load's 301 consumption of electrical power from the portionof the power distribution system 316, a Power Quality component 315 b,which measures power quality characteristics of the power on the portionof the power distribution system 316, and a billing/revenue managementcomponent 315 c, which computes the quantity and associated value of theincoming power. The power management components are connected to thenetwork via the data communications interface 312 using thecommunications protocol stack 312 (described in more detail below).

[0072] In one embodiment, a Billing/Revenue Management component on aback end server receives the billing and revenue computations over thenetwork 307 from the billing/revenue management component 315 c on theIED 310. These computations are translated into billing and revenuetracking data of the load 317 associated with the IED 310. TheBilling/Revenue Management component on the back end server then reportsthe computations to the appropriate party operating that particular backend server or subscribing to a service provided by the operator the backend server, either the consumer or provider of the electrical power.Additionally, the Billing/Revenue Management component 315 c on the IED310 or the Billing/Revenue Management component on the back end servercomputes usage and cost computations and tracking data of the associatedload and reports the data to the appropriate party. In a still anotherembodiment, IED 310 transmits billing and revenue data directly to theBilling/Revenue Management component over the network 307 and theBilling/Revenue Management component computes usage and costcomputations and tracking data of the associated load and reports thedata directly to the appropriate party. Furthermore, tariff datareceived from the utility by the Billing/Revenue Management component315 c is factored into usage or cost computations.

[0073]FIG. 3c illustrates a preferred embodiment of the communicationsprotocol stack 305 e. In the preferred embodiment the connection betweendevices coupled with the network 110 is established via the TransmissionControl Protocol/Internet Protocol (“TCP/IP”) protocol suite. Tofacilitate communications over a network or other communications medium,devices typically include a set of software components known as aprotocol stack. The protocol stack handles all of the details related tocommunicating over a given network so that other application programsexecuting on the device need not be aware of these details. The protocolstack effectively interfaces one or more application programs executingon the device to the network to which the device is connected.Typically, the protocol stack is arranged as a layered architecture withone or more software components in each layer. In the preferredembodiment, the protocol stack includes an application layer 321, atransport layer 322, a routing layer 323, a switching layer 324 and aninterface layer 325. The application layer 321 includes all of theapplications component software and/or power management componentsoftware. The application layer 321 is coupled with the transport layer322. Applications or software components in the application layercommunicate with the transport layer in order to communicate over thenetwork. In the preferred embodiment, the transport layer is implementedas the Transmission Control Protocol (“TCP”). The transport layer, usingTCP, divides communications from the applications of the applicationlayer 321 into one or more packets for transmission across the network.The transport layer adds information about the packet sequence to eachpacket plus source and destination information about what applicationcomponent generated the communication and to what application componenton the receiving end the communication should be delivered to oncereassembled from the constituent packets. The routing layer is coupledwith the transport layer and is responsible for routing each packet overthe network to its intended destination. In the preferred embodiment,the routing layer is implemented as the Internet Protocol (“IP”) andutilizes internet protocol addresses to properly route each packet of agiven communication. The switching and interface layers 324, 325complete the protocol stack and facilitate use of the physical hardwarewhich couples the device to the network. This hardware may include anEthernet interface, a modem, or other form of physical networkconnecting including RF based connections such as Bluetooth interfaces.Generally, the preferred embodiments are capable of communicating viaany network which transmits information utilizing the TCP and IP,collectively TCP/IP, protocols as are known in the art. TCP/IP isessentially the basic communication language of the both the Internetand private intranets. TCP/IP utilizes the communications protocol stackand can be described as comprising a TCP layer which manages thedecomposing and reassembling of messages from the application layer 321into smaller more manageable packets, and the IP layer which handles theaddressing of the packets. The IP layer comprises the routing layer 323,the switching layer 324 and the interface layer 325. The interface layer325, as described above, makes the physical connection with the networkutilizing connections such as Ethernet, dial-up-modems, Point-to-PointProtocol (PPP), Serial Line Interface Protocol (SLIP), cellular modems,Ti, Integrated Service Digital Network (IDSN), Digital Subscriber Line(DSL), Bluetooth, RF, fiber-optics or AC power line communications. Inan alternate embodiment multiple interface layers 325 are present. Forexample, the interface layer 325 contains both an Ethernet and cellularmodem thus enabling the IED to connect to the network with eitherinterface. This redundancy is advantageous if one interface isinoperable due to a local Ethernet or cellular network outage. It ispreferable that one or more of the application components in theapplication layer 321 implement TCP compatible protocols for theexchange of their communications over the network. Such TCP compatibleprotocols include the Instant Messaging protocol, file transfer protocol(“FTP”), or Hypertext Transport Protocol (“HTTP”). In addition, a SecureHTTP (S-HTTP) or Secure Socket Layers (SSL) may also be utilized betweenthe application layer 321 and the transport layer 322 for securetransport of data when HTTP is utilized. S-HTTP is an extension to HTTPthat allows the exchange of files with encryption and or digitalcertificates. SSL only allows authentication from the server whereS-HTTP allows the client to send a certificate to authenticate to theuser. T he routing layer 323 and the switching layer 324 enable the datapacket to arrive at the address intended.

[0074] In operation the IED monitors the power distribution system forevents such as wave shape deviation, sag, swell, kWh, kvA or other powerusage, consumption, or power quality events and disturbances. In oneembodiment, when the IED detects an event, it process the event andgenerates an email message using an email client application componentfor transport over the network to a back end data collection server. Rawdata 330, such as the error message generated from the IED or a billingsignal, is passed into the application layer's 321 Security Sub-layer321 a where it is encrypted before email protocol packaging 321 b takesplace. Once the data 330 has been encrypted and packaged, the message ispassed through the remaining IP layers where the message is configuredfor transmission and sent to the destination address. In one embodiment,the destination address is for a back end server implementing a datacollection application component. This back end server may be operatedby the consumer or supplier of electrical power or a third party asdescribed above. In an alternate embodiment the Security Sub-layer 321 aincludes authentication or encryption, or alternately the SecuritySub-layer 321 a is bypassed. The application layer may includeapplication components which implement protocols that are designed topass through a firewall or other type of software that protects aprivate network coupled with a publicly accessible network. Multipleredundant data messages may be sent from the IP layer to ensure thecomplete data packet is received at the destination. In the aboveoperation, the protocol stack, which includes an SMTP or MIME enabledemail client, is a scalable, commercial product such as the Eudorarmemail client manufactured by Qualcomm, Inc., located in San Diego,Calif. In an alternate embodiment data messages may also be sent toredundant destination email addresses to ensure delivery of the message.Quality of Service (QoS) may also be implemented, depending on thevolume of bandwidth required for the data, ensuring reliable and timelydelivery of the data. QoS is based on the concept that transmissionrates, error rates, and other characteristics of a network can bemeasured, improved and, to some extent, guaranteed in advance. QoS is aconcern for continuous transmission of high-bandwidth information. Thepower quality events, consumption, disturbances or other usage data maybe stored in the IED and sent to the destination address upon requestfrom an application component operating at the destination address, uponpre-determined time intervals and schedules, upon pre-defined events orin real time. In an alternate embodiment a IED may transport data orrequests to or receive data or requests from other IED's directly, alsoknow as peer-to-peer communications. Peer-to-peer is a communicationsmodel in which each party or device has the same capabilities and eitherparty or device can initiate communication sessions.

[0075] In an alternate embodiment the Security Sub-layer 321 a mayinclude multiple encryption keys, each conferring different accessrights to the device. This enables multiple users, such as a utility andcustomers, or multiple internal departments of a utility or customer, tosend or receive data and commands to or from the IED. For example acustomer's IED sends out two encrypted messages, one billing data andone power quality data, to the customer's office site. The billing datamessage is encrypted at a level where only the internal accountingdepartment has access to decrypt it. The power quality data message isencrypted at a different level where the entire company can decrypt themessage. Furthermore, in the preferred embodiment, commands sent to orfrom the IED are coupled with the appropriate encryption key. Forexample, the IED's Security Sub-layer 321 a may only permit billingreset commands to be received and processed if the command has beenauthenticated where the point of origin was the appropriate customer orutility. Further, encrypted email messages may also include variousencrypted portions, each accessible and readable with a differentencryption key. For example an IED sends out one message to both theutility and the customer containing billing data and power quality data.The data is encrypted with two different encryption keys so only theutility can decrypt the power quality data and only the customer candecrypt the billing data.

[0076] In operation the IED monitors the power distribution system 301for billing events such as, kWh or kvA pulses. In one embodiment the IEDmay store billing events and transport the data to the power managementapplication components operating on a back end server either uponrequest or upon pre-determined time intervals. Alternately the IED maytransport billing event data in real time to the back end server. Datamay be filtered through the either the Back End Server's or IED's powermanagement components or any combination or variation thereof, beforebeing entered into the Billing/Revenue Management component wherebilling, revenue, cost and usage tracking are computed into reviseddata. The Billing/Revenue Management components either stores thecomputations for future retrieval or pushes the revised data to theappropriate party, such as the consumer or provider of the electricpower system. Data can be retrieved upon command or sent or requestedupon a scheduled time.

[0077] In the preferred embodiment the back end server's operate in asimilar approach to the IED's. The back end server contains a transportprotocol stack and power management application components.Alternatively, a back end server could be a function or component of theIED, i.e., implemented as an application component.

[0078] The IED 402 implements power management functions on the wholeelectrical power distribution system 400 or just a portion thereof.Referring to FIG. 4a the IED 402 monitors the electrical power via thesystem 400 to a load 401 and reports events and data to the powermanagement application components 411 through the network 410. The powermanagement application components 411 are preferably operating on a backend server. The events and data are collected and processed through theautomated meter reading components, billing/revenue managementcomponents or a combination and variation thereof, and revised data orcommands are sent back to the IED through the network 410, enablingcontrol of the power flow and distribution of the loading on the powerdistribution system. The automated meter reading component allows forretrieval and collection of data for the customer, utility or thirdparty. The component further allows for schedule driven, event driven orpolling commands which are operable to push data onto the network.

[0079] The power management functions implemented by the IED's enablesthe back end servers or IED's to control power flow and distributionover the electrical power distribution system. Specifically the powermanagement application components process power measurement data andgenerate power measurement and reporting commands, transmitting them tothe back end servers or IED's for execution. Referring now to FIG. 4b,in one preferred operation a load is monitored by a IED where kvA andkWh pulse data are sent in real time over the network 424 to theApplication via email or another transport protocol. If pre-processingis required 425 a the raw pulse data is transported into a datacollection server or component where it is translated into a formatreadable by the billing/revenue management component 426. Alternately,the billing/revenue management component may be configured to receiveand process data without pre-processing 425 b. Once sent to thebilling/revenue management component 428 the data is compared andanalyzed for usage, consumption or billing revenue ranges against apre-determined tariff structure 432 where any anomalies, excess orshortages are reported back to the IED in the form of a command to apower management function which controls the power flow and loaddistribution accordingly 434. The components further contact therequired parties, such as the consumer or provider of the load, over thenetwork, forwarding power quality, billing, usage or consumption reportsor any power management functions that were required against the settariff structure.

[0080]FIG. 5a illustrates a preferred embodiment for a usage andconsumption management application of the power management architecture.The IED 502 implements a power management function of controlling thesource of electrical power for the load 501 from either energy supplier1 505 or energy supplier 2 506. The application is designed to takeadvantage a deregulated marketplace and operate the load 501 from themost cost efficient energy supplier at the given time period. Whichsupplier is most efficient may fluctuate frequently as a function of theenergy market and supply and demand for electrical power. Referring toFIG. 5b, the IED 502 contains a usage and consumption managementcomponent which receives tariff and cost structures from multiple energysuppliers 505, 506. The component receives usage and consumption fromthe Load 501 and compares actual usage against multiple tariffstructures choosing the most cost effective provider for a given load.Similarly the load management component 259, as shown in FIG. 2b, isutilized to connect and disconnect loads to and from the electricaldistribution system during either low and high rate and demand periods,hence reducing the electrical power costs and demand. In the preferredembodiment the load management component 250 is programmed to run in anautomated fashion based on feedback from the system, however in analternate embodiment the component is operated manually based on userinput.

[0081] For example, an IED 502 is connected to a power line 500 andassociated load 501. The IED 502 measures power usage by the load andtransmits this consumption data 514 over a network 510 to a usage andconsumption management application component operating on a back endserver 511. The Usage and consumption management component receives andtracks cost and usage 516, 518 and compares rates for actual usageagainst multiple suppliers bids 522. Suppliers have the option to eitherpush tariff structures to the application component or have tariffstructures polled over the network. Once the most cost effectivestructure is determined by the usage and consumption managementcomponent, a command or function is sent to the IED 502 with the newtariff structure 523, 524. Alternately, the new tariff structure isapplied across to the billing/revenue management component where billingis applied to the usage and revenue reports are forwarded onto theappropriate parties.

[0082] In another example the usage and consumption management componentdetermines all suppliers tariff structures are too expensive to warrantusage or consumption thus a command to reduce consumption to a desiredlevel is transmitted over the network to the IED 525. Furthermore, analternate embodiment includes application of real-time usage and costmonitoring of loads being measured by an IED and multiple energy anddistribution system suppliers.

[0083] In an alternate embodiment the usage and consumption component ispre-programmed to monitor and shed loads based on a exceeding a settariff structure. For example an IED 502 monitors a load 501 connectedto a power distribution system 500. Energy is supplied by an energysupplier 505. The IED contains a tariff structure that has a limit of$0.80/kWh during peak hours of 6 am to 6 pm and a limit of $0.60/kWh fornon-peak hours of 6 pm to 6 am. The IED 502 monitors the power usage ofthe load 501 vs. the actual tariff structure of the energy supplier andshuts the load 501 off if the actual tariff exceeds the limits of$0.80/kWh during peak times or $0.60/kWh during non-peak times.

[0084] The centralized power management component 255 allows thecentralization of work at one location, such as a centralized billingserver, load management server or master IED, which collects andprocesses data from various devices spread over the network. Inoperation, remote IED's connected to the network transmit data to thecentralized power management component where operations such as billing,load management, usage and consumption reporting are processed in onecentral location.

[0085] The distributed power management component 254 allows for thedistribution of work or data processing to various devices on thenetwork. In operation, an IED measures or detects an occurring orimpending catastrophic power quality event and alerts other downstreamIED's (on the power distribution network) of the event thereby givingthe downstream IED's an opportunity to disconnect or alter loads beforethe event reaches the downstream system and causes damage. The componentfurther includes a function that, upon detection of an occurring orimpending event, alerts downstream IED's or back end servers to alerttheir connected loads to either protect themselves from the outage byshutting down, or instructing them to shut down applications that maycause critical failure or damage if interrupted, such as writing to ahard-drive. FIG. 6 illustrates a preferred embodiment of the distributedpower management component in action. An Electrical power distributionsystem 600 distributes energy over distribution lines 601 which areconnected to multiple IED's 620, 622, 624, 626 which are present tocontinuously monitor the energy being fed onto their respective loads621 623 and generators 625 627 on a given branch and furthermore allIED's 620, 622, 624, 626 are connected via a network 610 as describedabove. IED's 616 618 are also present on the distribution system 600 tocontinuously monitor energy being transferred onto the system as awhole. It will be appreciated that the loads and generators may resideon multiple or separate consumer sites. In operation, a catastrophicpower quality event is detected on a load 623 by the attached IED 622.The IED 622 takes appropriate action, such as triggering a protectionrelay, on the load and further transmits communications of its actionsto upstream IED's 616 618. This ensures local containment of the eventby the IED 622 informing upstream IED's to not duplicate the action onthe larger system. Obviously retaining upstream IED's as a backup is notdiscounted in this operation. Alternatively, the operation is utilizedto coordinate downstream IED's over the network 610. For example anevent may be detected at the distribution system 600 by an IED 616monitoring the system 600 which triggers, for example, a protectionrelay. The IED 616 which triggered the protection relay communicates itsactions to downstream IED's 618 620 622 624 626 over the network 610allowing them to take appropriate intelligent action, such asdisconnection the generators 625 627. It can be appreciated that IEDapplications may include a combination of the centralized anddistributed power management components.

[0086] In one embodiment, a power reliability component 256 is providedin the IED to measure and compute the reliability of the power system.Power system reliability is discussed in commonly assigned U.S. patentapplication Ser. No. 09/724,309, entitled “APPARATUS AND METHOD FORMEASURING AND REPORTING THE RELIABILITY OF A POWER DISTRIBUTION SYSTEM”,filed Nov. 28, 2000, now U.S. Pat. No. ______, herein incorporated byreference. In the preferred embodiment the component 256 computes andmeasures reliability as a number of “nines” measure. The componentincludes a function which compiles the reliability of the power fromother components located on back end servers or IED's, giving a totalreliability. This function also enables a user to determine which partof the distribution system has the most unreliable power. Knowing thisenables the user to focus on the unreliable area, hopefully improvinglocal power reliability and thus increasing overall reliability.

[0087] For example, referring now to FIG. 7, an IED 711 is connected toa network 710 and measures the reliability of the power distributionsystem 701 which supplies power to loads 724 726 within a customer site705. The customer also provides a generator 726 which supplies power tothe loads 722 724 at various times. The customer measures the powerreliability of the system for the load 722 724 using the associated IED712 714 and considers it unreliable. One IED's 714 power reliabilitycomponent polls the other IED's 711 712 716 and determines theunreliable power source is coming from the generator 726. From this thecustomer can decide to shut off the power supply from the generator 726in order to improve the power reliability of the system.

[0088] In another embodiment, a power outage component 265 is providedin the IED which informs the appropriate parties of a power outage usingemail or other transport protocols. In the preferred embodiment an IEDis connected to a power system when a power failure occurs. The IED'spower outage component 265 contains hardware, such as a battery backupand modem, which enables the IED to transmit a power failure warning tothe appropriate parties, such as the utility or customer, such as byemail over a network as described above. Further, a cellular modem maybe utilized to call out to indicate the location of an outage. Physicallocating algorithms such as cellular triangulation or telephone callerID can be used to track or verify outage locations.

[0089] Peer to peer communications between IED's and between back endservers are supported by the peer to peer management component 257. Inthe preferred embodiment peer to peer communications are utilized totransport or compile data from multiple IED's. For example, as shown inFIG. 8, an IED 800 is connected to a network 810. Multiple loads 806 808draw power from a power utility's 803 power distribution line 801 andeach load is monitored by an IED 804 806. An IED 800 polls load andbilling data from all other IED's on the network on the customer site802 804. Upon request, the IED 800 then transmits the load and billingdata to the customer's billing server 814. In the preferred embodiment,the IED 800 communicates the load and billing data in a format whichallows software programs inside the customer billing server 814 toreceive the data directly without translation or reformatting.

[0090] Transmission of data in XML format allows a user to receive thedata in a readable self-describing format for the application intended.For example, traditional data file formats include comma-separated valuefiles (CSV), which contain values in tables as a series of ASCII textstrings organized so each column value is separated by a comma from thenext column's value. The problem with sending CSV file formats is therecipient may not be aware of each column's desired meaning. Forexample, a CSV file may contain the following information sent from arevenue billing application:

[0091] 45.54,1.25,1234 Elm Street, 8500

[0092] where 45.54 is the kWh used this month, 1.25 is the kWh usedtoday, 1234 Elm Street is the location of the device and 8500 is thetype of device. However, if the recipient of the CSV file was not awareof the data format, the data could be misinterpreted. A file transportedin XML is transmitted in HTML tag type format and includes informationthat allows a user or computer to understand the data contained withinthe tags. XML allows for an unlimited number of tags to be defined,hence allowing the information to be self-describing instead of havingto conform to existing tags. The same information is transmitted in XMLformat as:

[0093] <billing information>

[0094] <kWh month>45.54</kWh month>

[0095] <kWh day>1.25</kWh day>

[0096] <location>1234 Elm Street</location>

[0097] <device type>8500</device type>

[0098] </billing information>

[0099] Transmission in XML format allows the recipient to receiveXML-tagged data from a sender and not require knowledge of how thesender's system operates or data formats are organized. In a preferredembodiment communications between IED's connected to the network aretransmitted in XML format. An IED utilizes XML based client applicationcomponents included within the power management applications andtransmits the data in XML format so little or no post-processing isrequired. FIG. 9 illustrates an example of the preferred embodiment. AnIED 902 is connected to a power distribution line 900 and associatedload 901 owned by a customer 920. Power is supplied by a power utility's908 power generator 903. The power utility also has a utility billingserver 906 which compiles billing data from consumers drawing power fromtheir power generators. The IED 902 is connected to the utility billingserver via a network connection 910 and the IED 902 measures usage andconsumption of the load, and other values associated with billing. Theutility billing server 906 contains billing software, such as a MV90,which requires data in a specified format. Either upon request, or apre-scheduled times, the IED 902 transmits the usage, consumption andbilling data associated with the load 901 to the utility billing server906 in XML format. The customer also has a monitoring server 921 whichis dedicated to receiving billing data from the IED 902 and reportingusage and consumption to the appropriate parties, the monitoring server921 also reads data in a specified format for its associated monitoringsoftware. The IED 902 transmits the same usage, consumption and billingdata to the monitoring server 921 in XML format. By utilizing XML dataformats the data transmitted by the IED 902 can be read by multipleservers or IED's 902 that do not require knowledge beforehand of theorder or type of data that is being sent. In an alternate embodiment anIED 902 may also receive inputs from peripheral devices which may betranslated and combined in the XML transmission. For example, the load901 is a motor which contains a temperature probe. The temperature probeis connected to the IED 902 and allows the IED 902 to monitor the motortemperature in addition to power data on the power distribution line900. The IED 902 is programmed to act on the temperature input byshutting down the motor if the temperature exceeds a pre-definedcritical level by tripping a relay or other protection device (notshown). The IED 902 is further programmed to alert the customermonitoring server 921 and an alert pager 922 and if such an action takesplace. This alert transmission is sent in XML format so both the server921 and the pager 922, which may be configured to read incomingtransmissions differently, receive the alert transmission in the form itwas intended. It can be appreciated that the IED 902 can receive data inXML format from multiple sources without complete knowledge of theirfile transfer notations.

[0100] In an alternate embodiment the back end servers include softwarethat is generally included on a majority of existing computer systems,such as Microsoft Office™ software, manufactured by MicrosoftCorporation, located in Redmond, Washington which includes the softwareapplications Microsoft Word™ and Microsoft Excel™. The software receivesdata in a self describing format, such as XML, and the software includesoff the shelf applications and processes such as a Microsoft ExchangeServer, Microsoft Excel and associated Excel Workbooks, MicrosoftOutlook and associated Outlook rules, Microsoft Visio and associatedVisio Stencils, Template files, and macros which allow the user to viewand manipulate data directly from the IED. In one embodiment the IEDtransmission format makes use of existing standard software packages anddoes not require additional low level components, such as acommunications server communicating with a serial port, which arenormally required to interface to the IED communication ports. Further,the embodiment does not require a separate database, as the data isstored in the software programs. This allows a user to view data fromthe IED using standard computer software. For example, referring now toFIG. 10, an IED 1002 monitors a load 1001 and passes the monitored datato a monitoring server 1011. The data can be transmitted using a varietyof protocols, such as FTP, TCP/IP or HTTP, as described above. In thepreferred embodiment data is transmitted in an HTTP based form or anSMTP form where the HTTP form is a self-describing format such as XMLand the SMTP format is an email message. The monitoring server 1011includes Microsoft Exchange Server 1022, Visio 1021, Microsoft Excel1020 and Excel Workbooks 1023. The Excel software 1020 is capable ofreceiving data directly from the IED in a self-describing format, thusallowing the user to view real time load profiles or graphs and othermonitored data directly from the IED in real time. The Visio software1021 is also capable of receiving data directly from the IED in aself-describing format, thus allowing the user to process and view realtime data in Visio format. Alternately, the IED transmits power quality,load, billing data or other measured or monitored values to the ExcelWorkbooks 1023 via the Exchange Server 1022. The Excel or Visio softwareis then capable of retrieving historical data directly from theworkbooks.

[0101] Referring to FIG. 11, there is shown an exemplary screen displayof a Microsoft Excel worksheet which is coupled with the IED 1002 asdescribed above. In this example, the IED 1002 is a model 8500 meter,manufactured by Power Measurement Limited, in Victoria, BritishColumbia, Canada. The IED 1002 is coupled via a TCP/IP based networkwith a personal computer having at least 64 MB memory and 6 GB hard diskwith a Pentium™ III or equivalent processor or better, executing theMicrosoft Windows 98TM operating system and Microsoft Excel 2000. Thecomputer further includes Microsoft Internet Explorer™ 5.0 whichincludes an XML parser that receives and parses the XML data fro themeter and delivers it to the Excel worksheet. The worksheet displaysreal time data received directly from the IED 1002 in an XML format. Asthe IED 1002 detects and measures fluctuations in the deliveredelectrical power, it transmits updated information, via XML, to theworksheet which, in turn, updates the displayed data in real time. Notethat all of the features of the Microsoft Excel program are available tomanipulate and analyze the received real time data, including theability to specify mathematical formulas and complex equations which acton the data. Further, display templates and charting/graphing functionscan be implemented to provide meaningful visual analysis of the data asit is received. Further, the real time data can be logged for historicalanalysis. In one embodiment, the activation of a new IED 1002 on thenetwork is detected by the worksheet which cause automatic generation ofa new worksheet to receive and display data from the new device.

[0102] In still another alternative embodiment, the ability tocommunicate through a firewall or other private networksecurity/protection implementations, as described above, also known as“punch through”, is provided. As was described, in order to implementthe various power management applications on the disclosed powermanagement architecture, the IED's, back-end servers and theirconstituent application components must be able to intercommunicate withand among one another to share data and command and control information.Further, as was noted, the IED's, back-end servers and their constituentapplication components may be located anywhere, including within privateinternal networks, relying on the fabric of the public networkinfrastructure to link them together and facilitate their “machine tomachine” communications. However, concerns over enterprise networksecurity often result in the restriction of such communications betweenprivate/internal networks and public external networks such as theInternet. Unfettered communications over unknown or unregulatedprotocols or between unknown or unregulated clients, servers or hostsrepresent an inherent network security risk to an enterprise. As will bediscussed below, it is therefore advantageous to encapsulate/facilitatethese computer readable communications using protocols intended forhuman readable communications, such as electronic mail, hypertext/web orinstant messaging protocols, which are more benign and more easilyregulated and monitored, i.e. trusted.

[0103] A firewall is a software program, or combination of software andhardware, typically located on a network, that protects the resources ofa private network, such as an intranet, from users of other externalnetworks, such as the Internet, coupled with that private network. Thefirewall within an internal network, or intranet, allows internal usersaccess to the intranet but prevents outsiders from accessing the privatedata, and/or it controls which resources both the internal or externalusers have access to. Alternately, or in conjunction, the firewallrestricts outgoing connections to external network entities from theinternal user by restricting certain types of protocol connections ordata transfers. A firewall mediates/facilitates bidirectionalcommunication between two networks, typically external and internalnetworks, but in certain situations data or standard communicationsprotocols are only allowed outbound to the external network and notinbound from the external network. Alternately, select standardprotocols are enabled for both inbound and outbound communication.Standard communication protocols include FTP, NNTP or instant messagingprotocols, such as AOL™, Yahoo!™ or MSN™ instant messaging protocols. Itmay also include SMTP (port 25) type protocols known in the art or otherHTTP (port 80) type protocols. It will be appreciated that firewalls arewell known in the art.

[0104] A firewall examines each network packet to determine whether toforward it towards its destination. A firewall may also include or workwith a proxy server that makes external network requests on behalf oninternal users. The proxy server allows an enterprise, which has severalusers, to act as an intermediary between the users and the externalnetwork/internet so the Enterprise, such as a company's InformationServices department, can ensure security, administrative control and/oroffer caching services.

[0105] The firewall also acts as a screening method. For example, afirewall may screen requests to ensure they come from acceptable domainnames or Internet protocol addresses. Further, the firewall may alsoallow remote access into the private or internal network by the use ofsecure login procedures and authentication certificates. The termfirewall typically implies not only that firewall network hardware andsoftware is installed but also that a security policy is in place. Thesecurity policy refers to the configuration of the firewall as to whichinternal and external entities are permitted to communicate. Typicallythis includes defining which communications protocols will be allowed topass through and which computer systems or hosts, internal and external,will be allowed to communicate via those protocols. Such securitypolicies are typically implemented by the InformationTechnology/Services (IT or IS) departments of the enterprise.

[0106] Typical enterprises implement internal or local area networks forat least the purpose of allowing employees to communicate via electronicmail. Further, these mail servers are typically configured, along withthe firewall, to permit the exchange of electronic mail with entitiesoutside the enterprise. Mail servers may also act as a similar screeningmethod to restrict messages or access only to acceptable services orfrom acceptable users. For example, a mail server may screen incomingmessages to ensure that they come from acceptable or valid domain names,Internet protocol addresses or even specific user addresses. In oneembodiment a mail server may be instructed to only receive messages froma single user address, such as ied_data@company.com, or a valid domain@company.com. Further, the mail server typically must also be configuredfor each user or email client program that wishes to communicate usingthe server. For example, an email account must be set up for each userwithin the enterprise who is to be allowed to communicate via email.

[0107] In one embodiment disclosed herein, the IED is configured as anemail client with the email server and appears to the email server asany other user of email within the enterprise, creating, sending andreceiving emails via the server. These emails contain the computerreadable power management data and commands to other applicationcomponents within the power management application which are capable ofreceiving the email and parsing out the power management data orcommands. The IED may be configured to define or set any outgoingmessage criteria/parameters or to conform its communications to the useror enterprise domain address to ensure the mail server will accept anymessages the IED sends from the valid domain. In this way, the IED cantake advantage of the email server's capability to communicate via thefirewall to get messages out to the external network.

[0108] As described above, the ability of an IED to push or send data orcommands using the public Internet infrastructure allows IED's to beeasily scalable when implemented in a network type architecture. Byusing the existing resources of the enterprise in which the IED isinstalled, including the internal/local area network and its connectionwith the external network/Internet, the need for dedicatedcommunications media, such a telephone line, is eliminated. However,this ability to communicate requires that the data be able to get out ofthe internal/private network and to the external public network orInternet. As discussed above, with the advent of network security, thisrequires that the IED be able to send and receive its communicationsthrough the firewall. Sending data or commands, such as power managementcommands described earlier, using a protocol such as SMTP enabled emailclients, allows a user or IED to communicate through a firewall whilemeeting the demands for security by the enterprise. However, due tovarious security policies, discussed above, the enterprise's internalnetwork must be configured, in most cases, to allow such communication.

[0109] One method, as discussed above, is to configure the IED as anemail client on the enterprise's internal electronic mail server, wherethat server is capable of communicating electronic mail via thefirewall. In this case, the IED appears as any other user of the emailserver and is able to send and receive email via the firewall. The IEDneed only be configured to correctly interact with the mail server. Inanother embodiment, the IED is configured to interact with acommunications server, such as an electronic mail server or XML server,which is external to the enterprise's internal network. In this case,the security policy of the enterprise may need to be reconfigured toallow the firewall to pass the communications of the IED to an externalcommunications server such as an external mail server or external XMLserver. As will be discussed, in still another embodiment, the IED isconfigured to utilize a standard protocol typically already permitted bythe enterprise's security policy for communications via the firewall,such as the HTTP protocol. In this case, no reconfiguration of theenterprise's internal network is required for the IED to communicate viathe firewall.

[0110] In order to interact via electronic mail, whether with aninternal or external mail server, the IED includes an electronic mailclient application, as described above. It will be appreciated, thatdepending on the protocol and method of communications, the IED isequipped with an appropriately enabled client application, as describedabove. An exemplary SMTP enabled email client for IED's is theMeterM@il™ email client manufactured by Power Measurement, Ltd, locatedin Saanichton, B.C. Canada. Other protocols, such as Multi-PurposeInternet Mail Extensions (“MINE”) may also be used to transport data orcommands.

[0111] As described earlier in FIG. 3c, a security sub-layer 321 a ispresent on the application layer 321 where encryption before emailprotocol packaging takes place. In an alternate embodiment a securesockets layer (“SSL”) is utilized to ensure security between the IED andthe server or client which it ultimately connects to. SSL is acommonly-used protocol for managing the security of a messagetransmission. In the preferred embodiment, the SSL is included on theapplication layer 321, which includes all of the application softwarecomponent and/or power management components. SSL usespublic-and-private key encryption, which also includes the use ofdigital certificates. Digital certificates allow the recipient to verifythat the certificate is real, and hence the message is real and from anauthorized user. As described earlier, encryption can also be doneutilizing Pretty Good Privacy (PGP). PGP uses a variation of the publickey system, where each user has a publicly known encryption key and aprivate key known only to that user. The public key system andinfrastructure enables users of unsecured networks, such as theInternet, to securely and privately exchange data through the use ofpublic and private cryptographic key pairs. A security module, orsecurity application, includes the aforementioned encryption,authentication and encryption applications.

[0112] In an alternate embodiment a Network Time Protocol (“NTP”) orother form of time-syncing is utilized on the IED to ensure thetransferred message has the correct time and to ensure that the contentsof the message is derived using accurate time (i.e., interval energydata). NTP is a protocol that is used to synchronize computer or IEDclock times in a network, either external or internal. Accurate timeacross the network is important. Distributed procedures depend oncoordinated times to ensure proper sequences are followed or securitymechanisms depend on coordinated times across the network. For example,a supplier may initiate a startup of two generators, each connected toan IED. In order to achieve proper startup, the first and secondgenerator must be started in the correct order within a specified periodof time. The supplier sends a command to start the first generator at12:00 AM and the second generator at 12:01 AM. In order to ensure theproper startup sequence is done, both the IED's must be timesyncedtogether. As one can see, if one of the IED's has the incorrect internaltime the procedure may not occur in the correct order. Further, correcttime stamping of messages is important for real time or revenue relatedmessages. NTP typically applies to both the protocol and theclient/server programs that may run on the IED. In one embodiment, theIED NTP initiates a request to the network time server, internal orexternal. Alternately, the IED may receive the correct time to timesyncthe IED from the time server via a push mechanism.

[0113]FIG. 12 shows an example of a networked architecture withfirewalls. A firewall 1220 defines the internal network 1202, whichcomprises an intranet 1210 with IED's 1212 1214 coupled with theintranet 1210. The IED's 1212 1214 may be in turn connected to loads orgenerators or other devices requiring power management or other powermeasurement data. It can be appreciated that loads or generators, suchas fuel cells, turbines or flywheels, may be coupled with other types ofpower systems beyond electricity systems, such as power and gas. Asdescribed earlier power management data includes any data or informationutilized or created by an IED, such as a status information, loadinformation or electricity information used by an energy enterprise thatmay used in reporting or commanding or communicating to, with or from anIED. A database 1254 is connected to a server 1252, which may include amail server such as Microsoft Exchange™, which is in turn connected tothe Internet 1250. The network connections shown allow the server 1252to connect to the IED 1212. In an alternate embodiment, the externalnetwork 1204 contains another firewall 1225 thereby defining anotherinternal network which houses the server 1252 and the database 1254. Theuse of a firewall allows security to be present so the IED's 1212 1214located in the internal network 1202, or internal Ethernet network, areprotected from unauthorized access, and may restrict communications toother unauthorized sites or locations. For example the IED 1212 maycontain billing or other revenue certified data which is required to besent to the database 1254, which is located outside the secure firewall.The security contained in the firewall prohibits unauthorized users fromcollecting or viewing the billing data. The IED 1212 pushes or sendsbilling data on a scheduled or event driven basis by packaging thebilling data in an email message, which utilizes an SMTP protocol. Theemail message is sent through the firewall 1220 to the server 1252,which processes the data and forwards it onto the database 1254. It willbe appreciated that increased security, such as email encryption andauthentication as described earlier may be utilized to further preventunauthorized access to the billing data while in transport across theInternet 1250.

[0114] As shown in FIG. 13, Customer A 1305 contains an internal network1310 with various IED's 1312 1314 connected to the network 1310. Afirewall 1320 protects the internal network 1310 from users which mayattempt to access the IED's 1312 1314 or other network resources throughthe Internet 1350, or via some other type of external networkconnection. Customer B 1306 also contains an internal network 1326 withan IED 1322 connected to a transport box 1324, the transport box 1324,described in more detail below, is connected to the network. Theinternal network 1326 also contains a firewall 1330 which protects theinternal network from unauthorized users or access. An Enterprise 1360has a server 1352 and a database 1354 which are utilized to receive datafrom both Customer A 1305 and Customer B 1306. This data, such asrevenue billing data, or other power management data, is packaged by therespective IED 1314 on the respective internal network and sent using aSMTP protocol through the firewall 1320 to the server 1352. The server1352 contains a mail server, such as Microsoft Exchange™ which receivesand processes the data sent. The Enterprise 1360 has a database 1354which compiles the data sent by the respective Customers 1305 1306.Further, it will be appreciated that the Server 1352 can also send acommand or data packet to the IED 1312 using the same protocol.

[0115] In one embodiment the transport box 1324 allows an IED 1322,which does not have the ability to either directly connect to thenetwork 1326 or the ability to use an email transport protocol, toconnect to the Enterprise 1360. The IED, such as an electro-mechanicalwatt-hour meter, gives an output pulse, or other form of output data, tothe transport box 1324, which is equal to a pre-defined measurement suchas a kWh. In turn the transport box 1324 contains the ability to compileand translate the pulses or other output data from the IED 1322 intodata, such as billing data, and package and push or send the data oneither a pre-defined schedule, or an event driven schedule, to theEnterprise 1360. For example the TED 1322 emits a pulse to the transportbox for every kWh measured. The transport box 1324 is programmed to pushrevenue billing data, as measured by the IED 1322, on a weekly or otherscheduled basis to the Enterprise 1360. The transport box compiles thepulses, as sent by the IED 1322, into an email message containing thedata, encrypts the data, and sends the message through the firewall 1330to the Enterprise 1360. The Server 1352 receives the message from thetransport box 1324 and decrypts and authenticates the message beforesending the data to the database 1354. The database is then utilized toprovide billing to Customer B 1306 on a monthly basis. The use of afirewall 1330 ensures that an unauthorized user, such as Customer A, maynot access or alter the billing data contained in the transport box1324. In an alternate embodiment the transport box contains a dataconverter engine, such as an extensible markup language (“XML”) Engine,to convert the billing data into a pre-defined or readable data format,such as XML or Comma Separated Values (“CSV”).

[0116] Further, in an alternate embodiment, the Enterprise 1360, maycontact the Customer to enable a power management command, such as sheda load, on a load or device connected to an IED 1314. In operation apower management command is created or sent to the Server 1352 and thecorresponding “shed load” command is packaged in an email protocol, suchas SMTP, and sent to the IED 1314. A power management command may beincluded or reside in power management data. The use of an email messageallows the Enterprise 1360 to transmit information through the firewall1320. It can be appreciated that other transport protocols to transmitinformation through the firewall can be utilized, such as HTTP, HTTPTunneling, SOAP™ or instant messaging.

[0117] In an alternate embodiment the transport box is utilized to allowbi-directional communication through the firewall between the IED 1322and the Enterprise 1360. The Server 1352 sends an email message throughthe Internet 1350, the firewall 1330 to the transport box 1324,addressed to the IED 1322. The transport box 1324, which contains a mailserver, such as Microsoft Exchange™, receives and temporarily stores theemail message for pickup from the IED 1322. Alternatively, the MailServer 1328 may be external from the transport box 1324. Upon pickup,the IED 1322 can extract, process, permanently store the message andtake any necessary action the message may have included. This “store andforward” capability of the mail server 1328 allows the IED 1322 to onlyconnect to the Mail Server 1328 or Transport Box 1324 while thecorresponding message is held for retrieval. It can be appreciated thatalthough the IED 1322 has the ability to connect to the network but forreasons such as security utilizes the transport box 1324 or mail server1328 as a way to connect to the network and send messages either in onedirection or bi-directional as described.

[0118]FIG. 14 illustrates an alternate embodiment where the Mail Server1452 is located on the external network. Customer C 1405 comprises aninternal network 1410 with an IED 1412 and an internal mail server 1416connected to the network 1410. A firewall 1420 protects the internalnetwork 1410 from users which may attempt to access the IED 1412 via theInternet 1450, or some other type of external network connection. AnEnterprise 1460 has an enterprise mail server 1452 and a database 1454which are utilized to send or receive data or commands to or fromCustomer C 1405. In one embodiment a message is sent to the TED 1412. Inoperation, the message from the Enterprise 1460 is received and storedin the internal mail server 1416, and the IED 1412 contacts the internalmail server 1416 periodically to check for messages. If a message isfound on the internal mail server 1416 for the IED 1412 in question, theIED 1412 retrieves the message and acts or responds accordingly. In asecond embodiment the message is received and stored in the externalmail server 1452. This mail server 1452, which is located outside thefirewall 1420, also stores the message for the IED 1412 until the IED1412 retrieves the message and acts or responds accordingly. It can beappreciated that the IED connects to the internal mail server 1416 orthe external mail server 1452, which ever is utilized by the Customer1405, using protocols known in the art such as POP3 or Internet MessageAccess Protocol 4 (“IMAP”).

[0119] In another embodiment authentication and encryption of the emailmessage is performed to ensure that the email is not erroneouslyreceived by another IED 1312 and the command is conducted on the correctload or application. In another embodiment a proxy server is located onthe internal network however, in alternate embodiments, the IED maycontain a proxy server which can also act as a filter to protect the IEDfrom contacting or connecting to unauthorized sites. Further, it can beappreciated that the IED may have the ability to communicate to theinternet 1250 via a proxy server. In another embodiment the IED itselfmay contain a firewall to secure access as described above.

[0120] With the inherent insecurity of publicly accessible externalnetworks such as the Internet, private enterprises implementing internallocal area networks, such as Intranets, must take precautions. While thesafest alternative to prevent hacking, information theft, corporateespionage and other security breaches is to completely disconnect theinternal network from external network, this solution also shuts out thetremendous benefits of having access to such external networks, somewhich have been explained above. Therefore, network security devices andpolicies, such as firewalls, must be implemented to safeguard theinternal network while maintaining communication with the outside world.Automated power management applications operating on the disclosed powermanagement architecture, as described above, must deal with this realityand respect the enterprise's need for network security while employingthe intra-application component communications which span the internaland external networks to implement the power management application.

[0121] The disclosed embodiments meet these needs by providing a systemand method for communicating through a firewall that takes advantage ofthe existing network infrastructure of the enterprise withoutjeopardizing the security of that infrastructure. The disclosedembodiments do not require a dedicated communications medium such as atelephone line. Each IED is capable of connecting directly to theexisting network infrastructure, taking advantage of cabling, routers,switches, hubs, etc. that are already in place. Further, the disclosedembodiments do not require additional layers of data collection. EachIED is a standalone device capable of communicating with the back endservers or other data collection system within the power managementarchitecture. Additional dedicated intermediary devices are notnecessary to collect the power management data for the purpose ofcommunicating it over the internal network. Further, each IED is capableof initiating communications, either according to a schedule, or aspower management events are detected on the monitored power distributionsystem. This eliminates the need for in-bound “polling request”communications to the IED to cause it to send its data. By restrictingcommunications to outbound traffic only, the enterprise's networksecurity policies can be respected, and less burden is placed on theenterprise's network security staff in monitoring in bound networktraffic from unknown sources.

[0122] As described above, a generally accessibleconnectionless/scalable communications architecture is provided foroperating power management applications. The architecture facilitatesIED-supplier communications applications such as for automated meterreading, revenue collection, IED tampering and fraud detection, powerquality monitoring, load or generation control, tariff updating or powerreliability monitoring. The architecture also supports IED-consumerapplications such as usage/cost monitoring, IED tampering and frauddetection, power quality monitoring, power reliability monitoring orcontrol applications such as load shedding/cost control or generationcontrol. In addition, real time deregulated utility/supplier switchingapplications which respond in real time to energy costs fluctuations canbe implemented which automatically switch suppliers based on real timecost. Further the architecture supports communications between IED'ssuch as early warning systems which warn downstream IED's of impendingpower quality events. The architecture also supports utility/supplier tocustomer applications such as real time pricing reporting, billingreporting, power quality or power reliability reporting. Customer tocustomer applications may also be supported wherein customers can sharepower quality or power reliability data.

[0123] As described earlier, instant messaging (“IM”) protocols can beutilized to transport commands or data over a network from one IED toanother. The use of instant message applications offer severaladvantages over email or other types of communication applications dueto the real time and guaranteed end-user delivery of the message.Although real time communication is possible with email, real timecommunication is not always guaranteed or realistic. Further, unlikeemail, IM applications typically do not “store and forward” messages.Email offers three phases or states of operation in a given messagetransfer: 1) the message has been delivered or, 2) message has not beendelivered or, 3) the message is on it's way. The third state is anindeterminate state that leaves uncertainty in the success of thetransmission as an email message may be delayed while en route throughthe network or, worse yet, diverted and lost. Instant messagingprotocols eliminate this indeterminate third state by offering a binarystate of either received or not received, thereby offering guaranteedsuccess or failure of the message transmission. With today's dynamicmarket place, where power consumption and the associated fortunes ofutilities, and other entities involved in the power distribution market,can be made or lost in seconds, a user must be able to respondimmediately in real time with instantaneous knowledge and cannot affordto have indeterminate information.

[0124] While some instant messaging protocols do not require users ordevices to be connected on a public Internet type connection,alternative IM protocols, such as Jabber operate on an open Internetconnection utilizing an open source protocol developed bywww.jabber.org. Other IM applications, such as Microsoft's MSN™,manufactured by Microsoft Corporation located in Redmond, Wash. andExpress Messaging Server manufactured by ACD Systems Inc. located inSaanichton, British Columbia, Canada, are closed source platforms. Opensource refers to a program whose source code is made available for useor modification as users or developers see fit. Closed source refers toa program whose source code is typically proprietary and not availablefor use or modification to anyone but the original developers. IM can beutilized to have both person-to-person conversations andapplication-to-application conversations, such as web services, IProuting or data transfer. A person-to-application may also utilizeinstant messaging.

[0125] The instant message feature can be split into two types ofservice, centralized and distributed services. A centralized serviceuses an Instant Message Server to act as a central server application.Clients connect to the IM Server and the server logs and distributes theinformation provided by the clients. The IM Server automatically managesthe presence information for the users (clients) and applications (alsoclients), distributing the information as needed or requested. Presencewill be explained in detail below. In a centralized service, only theclients are connected to the server and the server is responsible fornegotiating the delivery and receipt of the client's data with the otherclients; all data transmitted over the instant message is transient inthe server and stored at the client. Another type of IM service is adistributed service which has no Instant Message Server per se, butrather each client is responsible to connect to all the other clients tomake their presence known and deliver their messages. Either type ofservice can be utilized to overcome firewall issues as instant messagingis typically added as an additional layer to the TCP/IP stack. Further,each type of service can be used either on an intranet (internal orprivate network) or over the public Internet infrastructure.

[0126] Typically, operation of a centralized IM application requiresboth the recipient (a client) and the sender (also a client) of theinstant message to be online at the same time. Further, the intendedrecipient must be willing to accept instant messages, as it is possibleto set the IM software to reject messages. The recipient can be anactual individual or a device, such as an IED, or a load or generatorconnected to an IED. An attempt to send an IM to a recipient who is notonline, or is not available or unwilling to accept the IM will result innotification that the transmission cannot be completed. If the recipientis willing or able to accept the IM, the message, or data inside themessage, is received by the recipient's device. Further, the recipienthas the capability to accept or reject the incoming message.

[0127] To further enhance the instant messaging capabilities presence isutilized. Presence is a way for a device to make it's connection oravailability known or available to the network it is connected to. Theconnection can be logical, and not necessarily physical as a wirelessdevice may be “present” on a network without any physical connection.Presence also allows a device to locate or identify a second device,wherever it may be on the network, as soon as the second device connectsto the network; it is an autonomous, contemporaneous broadcast ortransmission of the devices availability. There are several types ofpresence that can be used to signify the presence of a recipient orsender. Temporary Presence indicates where, on the network, therecipient was several minutes ago; Predicted Presence indicates wherethe sender thinks the recipient is now; Network Presence indicates therecipient client is logged in somewhere; Actual Presence indicates thatthe recipient is logged in somewhere; and Real Presence indicates thatthe recipient is logged in and communicating. In the preferredembodiment there are several sub-sets of Real Presence which areutilized. “Available” indicates the recipient is available to receivemessages; “Available but not on” indicates the recipient is availablebut the device is not on; “Available but on” indicates the recipient isavailable and the attached device is on; and “Available withrestriction” indicates the recipient is available but with restrictionto receive and execute commands. It can be appreciated by one skilled inthe art that there are several variations, extensions and permutationsof the above types of presence such as ‘away’, ‘do not disturb’,‘sleeping’ etc. Presence can also go beyond the above binary states tooffer insight into other necessary information. For instance presencemay also indicate information such as location, geographic, logical orphysical, or other application specific data such as general capacity,fuel, temperature, circuit capacity, % load, energy value or fault andtrip information, or “available with restriction” may also contain astatus note of “critical process online, will go offline at 13:03 PST”.Status is an extension of the presence of a device. While a deviceoffers the presence of “available”, the status may offer further deviceinformation.

[0128] Presence is detected, broadcasted or polled on a scheduled basis.For example, the presence is either requested or received every 1minute, or requested by a client. It is obvious to one skilled in theart that the 1 minute interval can be both increased or decreased tooffer alternate time resolution. In the case of a first clientrequesting the presence of a second client, the IM Server will poll thesecond client and make the information available to the first client.Alternately, the IM server will provide the second client presence tothe first client as the presence may by broadcasted or sent by thesecond client to the IM server thus allowing the IM server to receiveand update the presence without the need for polling. The ability toboth detect the presence, or receive a presence message from the device,offers the IM server the ability to track presence in substantially realtime. Alternately, presence can be detected, updated or broadcasted onan event driven basis.

[0129] The presence indications, as outlined above, can be altered inseveral ways. For example, a device may be instructed to switch from“available” to “available with restriction” upon the simple binary statedecision whether the device is either “inactive” and not in use and thus“available”, or “active” but in use and thus “available withrestriction”. Furthermore the “active” presence may be defined tosignify that the device is “active” if there is mouse or keyboardmovement from the operator, or if the processor is at, and maintains, acertain level of activity. It can also be appreciated that the devicecould alter its presence to “available with restriction” if theprocessor is in the middle of a critical process and cannot receiveanother command without sacrificing the critical process.

[0130] Presence can also be detected using other types of transportprotocols or commands such as email notification. For example a user maysend an email to a device instructing it to reply immediately with thedevice presence or status. Upon receipt of the return message the userchecks the timestamp to determine if the reply has been sent in theappropriate period of time to signify that the device is currentlyonline, and the reply content of the email can be used to give thepresence or status of the device. However, the possibility of anindeterminate response, i.e. no response is possible with email whichmay leave the requester in a hanging state. Further, the use of email todetermine presence, combined with the aforementioned security offers theability to determine the presence of a device securely. This isimportant because a user may want to determine the presence or status ofa device, but not want another user, such as the competition, to be ableto determine the status of their devices. It can also be appreciatedthat the use of aforementioned security module can be coupled with aninstant message or the instant message server itself.

[0131] In the preferred embodiment the Instant Message Server containstwo services, the Presence Service and the Instant Message Service. ThePresence Service accepts presence information, stores and distributes itwhereas the Instant Message Service serves to accept and deliver InstantMessages. It will be appreciated that these two services can be combinedor implemented separately depending on the application. The advantagesof having the presence service separate from the instant message serviceallows other applications to make use of the services independently. Forexample, a client may wish to use the presence service in conjunctionwith an email service or other type of communication protocols thusallowing the client to detect and reveal the availability of anotherclient on the network before sending a message. In another example aclient utilizes instant messaging without the use of presence, but theclient is instructed to use an email service as a backup if the instantmessage is rejected due to the intended recipients unavailability. Inthis example presence is not required as the instant message is rejectedif a connection cannot be made. It will be appreciated that the successor failure of an instant message is, itself, an indication of presence.

[0132]FIG. 15a illustrates a network with an instant message serverresiding on the network. Clients, such as computers 1510 and IED's 15041508 connected to their associated loads 1502 and breakers 1506, arecoupled with the network 1501. In this embodiment the IM server 1500 isconnected with the network 1501. It can be appreciated that the IMserver may be connected with the network 110 shown in FIG. 1 as well(not shown).

[0133]FIG. 15b illustrates an architecture that allows a client to showits status and/or presence to an IM server. When a client, or user, goesonline 1520, the client presence is determined 1525 and sent to theInstant Message Server 1530, or other server which acts as the presenceserver. Two types of events can then trigger a presence change: 1) Ifthe client or user detects or has an event which may alter its status orpresence then the presence or status is re-determined 1525 and 2) if apre-determined time has elapsed 1540 without any event then the presenceor status is determined again 1525. It is appreciated that thepredetermined time can be set by either the client or requested by theserver and, in either case, be defined to give substantially real timepresence as required by the client, user or server. In the case of adistributed system, block 1530 would provide for broadcasting thepresence to all available devices on the presence or instant messagenetwork. It will be appreciated that the instant message network can bea private intranet where a collection of clients and instant messageservers are connected on a common network, such as an Ethernet network,or the instant message network may embody a subset of the larger publicInternet infrastructure with the instant message server attached to aspecific internet protocol address.

[0134]FIG. 15c illustrates the architecture involved for the server toreceive and update the presence of clients in a centralized IMapplication. When the server receives the initial presence 1550 of theclient, the presence is updated 1555 on the server and made availablefor all other appropriate clients to view. In one embodiment, thepresence may be encrypted or hidden from unauthorized users. At block1560, the server waits for a predetermined time to elapse before theserver checks to see if the presence is received again 1565. Thisfeature ensures that if a client goes offline, but is unable to send anerror, the server will automatically update the client presence to showa presence error 1570. Alternately, the server may be configured tocontact the device directly using a predetermined communication means torequest a presence update 1575, such as an email command or instantmessage requesting a particular reply. It will be appreciated by oneskilled in the art that the same architecture applies to a distributedsystem except the functions of the server are located on/distributed toeach device.

[0135]FIG. 16 illustrates an exemplary communications architectureincluding multiple IED's and associated loads and generators connectedto a utility, utilizing an Instant Messaging Server in a centralizedsystem. In this example, the Presence Server is incorporated into thefunctionality of the IM Server 1620 but it can be appreciated that thePresence Server can be a separate, independent server. A first IED 1606is connected to a load 1608 and a second IED 1610 to a generator 1613,both of which are available to be shut down or turned on upon requestfrom the utility during high power demand times. An Instant MessageServer 1620 connects the Power Utility 1600 to the IED's 1606 1610. Inone exemplary operation, the utility 1600 may need to reduce the load onthe power grid 1622 by either reducing the load 1608, or starting thegenerator 1613. In one embodiment, the utility 1600, using presence,detects the load 1608 is ‘available and on’, and the generator 1613 is‘available but not on’. A power management command, which includes ashed load command, is sent to the IED 1606 and the load 1608 as aninstant message using the IM server 1620. The IED 1606 accepts thecommand, executes the appropriate function and replies to the utility1600 using a second instant message, via the IM server 1620, indicatingthat the appropriate load has been shed. The presence of the load 1608now indicates ‘available but not on’. Alternately, the IED 1606 maydetermine that the load 1608 is a critical load, or is in the middle ofa critical process and cannot be shut down. In this case the IED 1606then rejects the message from the utility 1600 or, further yet, altersthe load's 1608 presence to show ‘available with restriction’. In thisembodiment the utility 1600 determines that in order to reduce the loadon the power grid 1622 it must start the generator 1613. As the IMpresence detects that the generator is available for startup, theutility 1600 sends a command to the IED 1610 requesting startup using aninstant message protocol. The IED 1610 accepts the message and initiatesstartup of the generator 1613. The TED also replies to the utility 1600,sending a startup confirmation in an instant message through the IMserver 1600. During the generator 1613 startup phase the generatorpresence is altered from ‘available but not on, to ‘available but withrestriction’. This is important because a device, while in startup mode,may be damaged if another command is sent to shut it down before it isfully started up and can initiate a shut-down procedure. Once thegenerator is in full operation the presence is changed to ‘available andon’. Alternately, presence is used to determine if there is an errorwith the load 1608 such as if the utility 1600 determines that the load1608 is not present, or unavailable, without reason. In this case‘unavailable’ is signified and the utility 1600 knows an error hasoccurred that needs to be addressed.

[0136] It can be appreciated that the utility 1600 can send instantmessages to the load 1608 and generator 1613, or their associated IED's1606 1610, without the use of presence, and utilize the IED's 1606 1610,and IM responses therefore, to determine if the associated loads,generators or connections to devices thereto are available to process orexecute the command contained within the instant message. It can also beappreciated that the same type of distributed system is contemplated butwithout the Instant message Server 1620. In this situation each clientis responsible to both indicate they are online and poll the otheronline clients for their presence information.

[0137] Instant messaging also offers the ability to receive co-dependentor multiple separate messages, and allows a recipient to either reply tomultiple messages concurrently or independently. This ability allows apower utility 1600 to send a shared message to multiple IED's 1606 1610with identical instructions.

[0138] In an alternate embodiment the use of instant messages offers theability to send software, firmware or other computer upgrades to devicesusing instant messages with presence. A power utility 1600, or a thirdparty manufacturer 1650 may require that the IED's 1606 1610 be upgradedwith new firmware. In operation the utility 1600, utilizing presence,determines if the devices 1606 1610 are available to be upgraded and, ifthe devices 1606 1610 are shown as available to be upgraded, the upgradeis sent via an instant message. It can be appreciated that this upgradecan come in the form of an actual file upgrade, or a command for thedevice to connect to another device or server to download and implementthe upgrade as disclosed in U.S. patent application Ser. No. 09/792,701,entitled “SYSTEM FOR IN THE FIELD CONFIGURATION OF INTELLIGENTELECTRONIC DEVICES”, filed on Feb. 23, 2001 which is herein incorporatedby reference.

[0139] In another embodiment, instant messaging also includes securityprotocols such as encryption, decryption and authentication, similar tothe security described earlier in relation to, among other things, thesecurity module. These security applications, such as digitalcertificates, tracking ID's or other algorithms, are utilized on theopen source systems. It can be appreciated by one skilled in the artthat similar private security applications are utilized on the closedprotocols, such as on Microsoft's MSN instant messaging. Further, thesecurity applications described can also be utilized to scan or stop avirus or other type of malicious or damaging program, command or event,such as a denial-of-service attack, from being sent via thetransmission, either intentionally or unintentionally. A virus scanneror similar detection software known in the art is placed on either thesenders or recipients device to automatically check if a virus isattached to the incoming our outgoing message. Alternately the securitypolicies are embedded in the firewall to offer self protection frommalicious attacks or viruses.

[0140] As mentioned earlier, a firewall is an application that typicallyprotects entry from a publicly accessible network that is coupled to aprivate network. In an alternate embodiment a third party 1650, such asa Billing Company, resides behind a firewall 1640. Communication betweenthe Billing Company, the Power Utility 1600 and IED's 1606 1610 is madepossible with the use of the IM Server 1620 as instant messages are ableto pass through a firewall 1640 using technology known in the art, suchas HTTP tunneling. In operation the Billing Company 1650 uses presenceto determine if the utility is present and available to receive amessage. If so the Billing Company 1650 transmits a tariff structuremessage through the firewall 1640 to the Power Utility 1600 via the IMServer 1620. From there the Power Utility 1600 can take appropriateaction, such as reduce the loads on the power grid 1622, as describedearlier. Alternately the Billing Company 1650 can transmit other typesof messages, such as real time pricing.

[0141] In another alternate embodiment, where security is necessary onthe secure side of a firewall 1660, a computer 1662 is connected to anIED 1664, and the IED 1664 to the power grid 1622. In operation the IED1664 is used to determine the power parameters directly from the powergrid 1622 and the computer 1662 initiates connection through thefirewall 1660 to the IM server 1620, pushing the presence of the TED1664. At this point there is now a connection between the IM server 1620and the secure side of the firewall 1660 where the TED 1664 resides.

[0142] In yet another embodiment, a first client attempting to detect asecond client that they wish to contact that is not “present” or“available”, may instruct the instant message application to show analert when the second client becomes available, or send a pre-storedmessage to the second client upon their availability. This allows aclient or user to mix the “store and forward” technology with an instantmessage protocol technology. For example, a client may wish to upgradefive devices on a network by sending an upgrade patch attached to theinstant message. All of the intended recipient devices are availableexcept one, who's presence shows as “on but unavailable to receivecommands”. The client sends a co-dependent message with the attachedupgrade file and associated upgrade commands. The client then receivesfour positive notification from all devices that the message wasreceived and one negative notification stating that the device isunavailable to upgrade at this time. The client then initiates a routinewhich continually checks the fifth device until the presence is changedto “available” and then the upgrade message is sent. This routine mayhave a pre-defined time-out period, the elapse of which indicates anerror that needs to handled. As described earlier the co-dependentmessage allows the client to send one message to the entire group ofusers in place of single multiple messages.

[0143] As mentioned earlier presence can be utilized to show the statusof a device beyond just the “active” status or application specific dataor status parameters, such as load capacity or breaker status. Wherepresence is limited and detailed status information cannot be reported,instant messaging can be utilized to retrieve the required data.Furthermore, programmed instant messaging alarming can be utilized tooffer status updates at pre-configured status levels of a device or uponcommand from a user. For example a generator may be generating at x %capacity with y % available; the same can be said about a load on acircuit main or breach circuit. At 80% loading a “high loading status”is reached, at 95% loading a “trip point eminent status” is reached andat 0% loading a “breaker tripped status” is shown. In operation instantmessages are used to transmit these pre-determined status points to theoperator when they are reached. Additionally the use of presence todetect that the status update message has been received offers theability of a device to ensure a user is available that can respond tothe status report. For example, a circuit breaker reaches 80% loadingand thus is programmed to send a status update using an instant messageto the associated plant operators. When the circuit breaker reaches 95%loading, and thus is showing a “trip point eminent status”, the circuitbreaker is programmed to, using presence again, check to see if a plantoperator is online and available to receive the status update as aloading of this level needs immediate attention. If the operator shows“unavailable” the circuit breaker is then programmed to check otherplant operators availability. This ensures that a plant operator willreceive the status update and hopefully act appropriately. It can beappreciated that many other alarms, such as “generating but with lowfuel”, “service required” or “generator temperature exceeded” on bothgenerator devices or associated loads, can be programmed into anydevices that have instant messaging and/or presence capability.

[0144]FIG. 17 illustrates an Instant Message Server connected to aBranch Circuit System. A master IED 1700 has multiple IED's 1702 17041706 downstream of the master IED 1700, each second tier branch 17611762having loads 1712 1716 1720 1732 1736 1740 and IED's associated witheach load. The use of instant messaging between the IED's allows thesystem, or a segment of the system, to compile and describe the state ofthe system and thus make informed decisions such as changing loads toavoid an entire system outage. In operation each IED is connected to theInstant Messaging Server 1750 (connection not shown). In a distributedsystem it is appreciated that a master IED 1700, or other IED, maycontain the instant message or appropriate presence server. The upstreamIED's 1700 1702 1704 1706 use instant messaging and presence to sum theinformation about each branch 1760 1761 1762, and allow the upstreamIED's to make informed decisions about the branch. For example themaster IED 1700 detects a changing load on a branch 1762 and must make adecision based on availability of altering loads to different circuits,rerouting power or bringing additional generators online.

[0145] It is therefore intended that the foregoing detailed descriptionbe regarded as illustrative rather than limiting, and that it beunderstood that it is the following claims, including all equivalents,that are intended to define the spirit and scope of this invention.

We claim:
 1. An electrical power management architecture comprising: anetwork; at least one electric meter coupled with said network; and aninstant message server coupled with said electric meter and saidnetwork, said electric meter operative to generate a first instantmessage to said instant message server and receive a second instantmessage from said server.
 2. The electrical power managementarchitecture of claim 1 further comprising a presence server coupledwith said network and operative to autonomously indicate a connection ofsaid electric meter with said network, said connection characterized bya presence.
 3. The electrical power management architecture of claim 2further wherein said presence server indicates said presence of saidelectric meter in substantially real time.
 4. The electrical powermanagement architecture of claim 2 further wherein said presence serverreceives said presence of said electric meter from said electric meter.5. The electrical power management architecture of claim 2, saidpresence server further including a security module, said securitymodule operative to encrypt said presence.
 6. The electrical powermanagement architecture of claim 2 wherein said presence indicates saidelectric meter is available.
 7. The electrical power managementarchitecture of claim 2 wherein said presence indicates said electricmeter is available with restriction.
 8. The electrical power managementarchitecture of claim 2 wherein said presence indicates said electricmeter is active.
 9. The electrical power management architecture ofclaim 2 wherein said presence indicates said electric meter isunavailable.
 10. The electrical power management architecture of claim 2wherein said presence shows said electric meter is decoupled from saidelectrical power management architecture.
 11. The electrical powermanagement architecture of claim 2 further wherein said presence serverpolls said presence of said electric meter.
 12. The electrical powermanagement architecture of claim 11 further wherein said presence serverpolls said presence of said electric meter using an electronic mailmessage.
 13. The electrical power management architecture of claim 11further wherein said presence server polls said presence of saidelectric meter on a scheduled basis.
 14. The electrical power managementarchitecture of claim 1, wherein said instant message server isoperative to facilitate communication of data using a third instantmessage.
 15. The electrical power management architecture of claim 14wherein said third instant message is sent to a plurality of electricmeter's, each of said plurality of electric meters being coupled withsaid network.
 16. The electrical power management architecture of claim14, wherein said third instant message comprises power management data.17. The electrical power management architecture of claim 16 whereinsaid power management data comprises power quality data.
 18. Theelectrical power management architecture of claim 16 wherein said powermanagement data comprises upgrade data.
 19. The electrical powermanagement architecture of claim 16 wherein said power management datacomprises power management commands.
 20. The electrical power managementarchitecture of claim 1, wherein said instant message server is locatedon said electric meter.
 21. The electrical power management architectureof claim 1, wherein said instant message server is centralized.
 22. Theelectrical power management architecture of claim 1, wherein saidinstant message server is distributed.
 23. The electrical powermanagement architecture of claim 1 further comprising a second networkand a firewall, said firewall operative to securely couple said networkwith a second network.
 24. The electrical power management architectureof claim 1, wherein said network comprises a publicly accessiblecommunications network.
 25. The electrical power management architectureof claim 1, wherein said network comprises a Transmission ControlProtocol/Internet Protocol (“TCP/IP”) based network.
 26. The electricalpower management architecture of claim 25 wherein said network comprisesthe Internet.
 27. The electrical power management architecture of claim25 wherein said network comprises an intranet.
 28. The electrical powermanagement architecture of claim 1 wherein said electric meter is arevenue meter.
 29. The electrical power management architecture of claim1 wherein said electric meter is characterized by a presence, saidelectric meter operative to broadcast said presence.
 30. An electricalpower management architecture comprising: a network; a presence server;at least one electric meter coupled with said network, said electricmeter operative to autonomously indicate said connection of saidelectric meter on said network, said presence server operative toreceive said autonomous indication.
 31. The electrical power managementarchitecture of claim 30 further wherein said autonomous indicationcomprises a presence of said electric meter.
 32. The electrical powermanagement architecture of claim 30 further comprising an instantmessage server coupled with said network.
 33. The electrical powermanagement architecture of claim 30 further wherein said autonomousindication is transmitted to a plurality of available recipients on saidnetwork.
 34. The electrical power management architecture of claim 30wherein said autonomous indication is further characterized by a status.35. The electrical power management architecture of claim 30 furtherwherein said presence server polls said autonomous indication of saidelectric meter.
 36. The electrical power management architecture ofclaim 35 further wherein said presence server polls said autonomousindication of said electric meter using an electronic mail message. 37.The electrical power management architecture of claim 35 further whereinsaid presence server polls said autonomous indication of said electricmeter on a scheduled basis.
 38. The electrical power managementarchitecture of claim 30 further wherein said presence server indicatessaid autonomous indication of said electric meter in substantially realtime.
 39. The electrical power management architecture of claim 30further wherein said presence server receives said autonomous indicationof said electric meter from said electric meter.
 40. The electricalpower management architecture of claim 30, said presence server furtherincluding a security module, said security module operative to encryptsaid presence.
 41. The electrical power management architecture of claim30, wherein said presence server is located on said electric meter. 42.The electrical power management architecture of claim 30, wherein saidpresence server is centralized.
 43. The electrical power managementarchitecture of claim 30 wherein said autonomous indication indicatessaid electric meter is available with restriction.
 44. The electricalpower management architecture of claim 30 wherein said autonomousindication indicates said electric meter is active.
 45. The electricalpower management architecture of claim 30 wherein said autonomousindication indicates said electric meter is unavailable.
 46. Theelectrical power management architecture of claim 45 further whereinsaid electric meter is available.
 47. The electrical power managementarchitecture of claim 30 wherein said autonomous indication indicatessaid electric meter is available.
 48. The electrical power managementarchitecture of claim 30 wherein said autonomous indication furtherindicates said status of said electric meter.
 49. The electrical powermanagement architecture of claim 30 wherein said autonomous indicationindicates said electric meter is decoupled from said electrical powermanagement architecture.
 50. The electrical power managementarchitecture of claim 30, wherein said network comprises a publiclyaccessible communications network.
 51. The electrical power managementarchitecture of claim 30, wherein said network comprises a TransmissionControl Protocol/Internet Protocol (“TCP/IP”) based network.
 52. Theelectrical power management architecture of claim 51 wherein saidnetwork comprises an intranet.
 53. The electrical power managementarchitecture of claim 30 wherein said autonomous indication is broadcastonto said network.
 54. The electrical power management architecture ofclaim 30 wherein said electric meter is a revenue meter.
 55. Theelectrical power management architecture of claim 30 further comprisingan instant message server coupled to at least one intelligent electronicdevice (“IED”) and said network.
 56. A method of monitoring presence ofat least one intelligent electronic device (“IED”) in an electricalpower management architecture, said method comprising: (a) coupling saidIED with a network, said IED being characterized by said presence; (b)transmitting, autonomously, said presence of said IED onto said network;(c) receiving said presence of said IED at a presence server coupledwith said network; and (d) monitoring said presence of said IED.
 57. Themethod of claim 56, further comprising said monitoring further comprisesupdating said presence of said IED on said presence server.
 58. Themethod of claim 56, wherein said receiving further comprises displayingsaid presence of said IED on said presence server.
 59. The method ofclaim 56, further comprising: (e) encrypting said presence.
 60. Themethod of claim 56, wherein said monitoring further comprises monitoringaccording to a pre-defined schedule maintained by said presence server.61. The method of claim 56, wherein said monitoring further comprisesmonitoring according to a pre-defined schedule maintained by said IED.62. The method of claim 56, wherein said transmitting further comprisestransmitting said presence in response to an occurrence of a eventmonitored on said IED.
 63. An electrical power management architecturecomprising: a network; a presence server coupled with said network; atleast one intelligent electronic device (“IED”) coupled with saidnetwork, said IED operative to autonomously indicate said connection ofsaid IED on said network, said presence server operative to receive saidautonomous indication.
 64. The electrical power management architectureof claim 63 wherein said IED is a relay.
 65. An electrical powermanagement architecture comprising: at least one intelligent electronicdevice (“IED”) coupled with a portion of an electrical power system andfurther coupled with an internal network; a firewall, said firewalloperative to securely couple an external network with said internalnetwork; and a network interface operative to couple said IED with saidinternal network and facilitate a communications, initiated by said IED,of first power management data through said firewall from said internalnetwork to said external network.
 66. An electrical power managementarchitecture for managing an electrical power distribution systemcomprising: a network; at least one intelligent electronic device(“IED”) coupled with a portion of said electrical power distributionsystem and further coupled with said network, each of said at least oneIED operative to implement a power management function in conjunctionwith said portion of said electrical power distribution system, saidpower management function operative to respond to at least one powermanagement command and generate power management data, each of said atleast one IED comprising: a first network interface operative to couplesaid at least one IED with said network and facilitate autonomoustransmission of said power management data and receipt of said at leastone power management command over said network; and a security modulecoupled with said first network interface and operative to preventunauthorized access to said power management data; said architecturefurther comprising: a power management application coupled with saidnetwork and operative to receive and process said power management datafrom said at least one IED and generate said at least one powermanagement command to said at least one IED to implement said powermanagement function.
 67. The electrical power management architecture ofclaim 66 wherein said power management data and said power managementcommands are communicated as instant messages.